Skip to content

Prevent reports from reading partially written Allure attachments - #1371

Open
baev wants to merge 1 commit into
mainfrom
fix-results-write
Open

Prevent reports from reading partially written Allure attachments#1371
baev wants to merge 1 commit into
mainfrom
fix-results-write

Conversation

@baev

@baev baev commented Aug 5, 2026

Copy link
Copy Markdown
Member

Context

Allure results and attachments are now published with an atomic move after writing completes, preventing report generation and TestOps from picking up incomplete files on supported filesystems. This is especially important for large artifacts such as test-session video recordings, which could otherwise appear corrupted when a report starts immediately after the tests finish.

Filesystems that do not support atomic moves retain the existing replace behavior instead of losing the completed file. Failed publications also clean up their temporary files.

Checklist

@baev baev added the pr:improvement Change that improves some user experience but can't be considered as a new feature label Aug 5, 2026
@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown

Allure Report Summary

Name Duration Stats New Flaky Retry Report
Allure Java – Pull request #1371 26m 30s Passed tests 2086 10 0 0 View
Allure Java GitHub actions run (2026-08-05T18:10:36.524Z) 26m 30s Passed tests 2086 10 0 0 View

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr:improvement Change that improves some user experience but can't be considered as a new feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants