Skip to content

Write Allure result files atomically - #924

Merged
delatrie merged 2 commits into
masterfrom
atomic-write
Sep 18, 2026
Merged

delatrie merged 2 commits into
masterfrom
atomic-write

Conversation

@delatrie

@delatrie delatrie commented Sep 18, 2026 •

Copy link
Copy Markdown
Contributor

Context

The PR implements atomic writes: Allure result files are first written with the .tmp suffix then get renamed to their final names with os.replace.

@delatrie
delatrie merged commit 5c72005 into master Sep 18, 2026
53 checks passed
@delatrie
delatrie deleted the atomic-write branch September 18, 2026 19:43
lorenzhs added a commit to firebolt-db/firebolt-python-sdk that referenced this pull request Oct 7, 2026
Allure 2.16.1 introduced atomic report writes: io.open writes the
temporary file on the real filesystem, but pyfakefs intercepts
os.replace and searches the fake filesystem. Exclude the actual
Allure modules so both operations use the real filesystem.

Upstream: allure-framework/allure-python#924

Validation: Python 3.9.25, Allure 2.16.2, pyfakefs 5.6.0; full unit
suite with coverage and Allure enabled: 778 passed, 1 skipped.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants