Skip to content

fix(reporter): keep other shards' blob reports in the output dir - #43035

Open
Ashraf Ali (ashrafiucse) wants to merge 2 commits into
microsoft:mainfrom
ashrafiucse:fix-43013
Open

Ashraf Ali (ashrafiucse) wants to merge 2 commits into
microsoft:mainfrom
ashrafiucse:fix-43013

Conversation

@ashrafiucse

Copy link
Copy Markdown
Contributor

Summary

  • Sharded blob runs share the output dir, but every run removed the whole dir before writing its own report, so each shard deleted the reports of previously completed shards (merge-reports then only saw the last shard).
  • When config.shard is set, only remove this shard's own report file (best-effort with retries, like removeFolders); non-sharded runs keep cleaning the output dir as before.
  • Note: a stale report from a differently-parameterized previous run (e.g. a non-sharded report.zip) now persists alongside new shard reports, since a sharded run only owns its own slot.

Fixes #43013

Sharded blob runs share PLAYWRIGHT_BLOB_OUTPUT_DIR, but each run
removed the whole dir before writing its own report, so every shard
deleted the reports of previously completed shards. When sharded,
only remove this shard's own output file now; non-sharded runs keep
cleaning the dir.

Fixes: microsoft#43013
A locked report file on Windows could make fs.promises.rm reject and
fail the run; swallow the error like removeFolders does since the
subsequent write truncates the file anyway.

Fixes: microsoft#43013

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: blob reporter empties folder PLAYWRIGHT_BLOB_OUTPUT_DIR

1 participant