Skip to content

ci: fix duplicate failsafe-summary.xml upload in sharded container-e2e-test - #2240

Merged
velo merged 1 commit into
ci/shard-container-e2e-testsfrom
chunk/fix-container-e2e-duplicate-failsafe-summary
Jul 29, 2026
Merged

ci: fix duplicate failsafe-summary.xml upload in sharded container-e2e-test#2240
velo merged 1 commit into
ci/shard-container-e2e-testsfrom
chunk/fix-container-e2e-duplicate-failsafe-summary

Conversation

@circleci-app

@circleci-app circleci-app Bot commented Jul 29, 2026

Copy link
Copy Markdown

Summary

  • Both parallel nodes in container-e2e-test produce a failsafe-summary.xml file under the same path (sqrl-testing/sqrl-testing-container/target/failsafe-reports/).
  • When CircleCI archives test results from both shards, the duplicate failsafe-summary.xml filename causes the "Uploading test results" step to fail on both nodes (job 10082, step 112).
  • The actual TEST-*.xml files are correctly split across shards (11 distinct test classes each) — only the summary file collides.

Fix: Replace the direct store_test_results path with a run step that copies only TEST-*.xml files into a shard-indexed subdirectory (~/test-results/container-${CIRCLE_NODE_INDEX}/) before archiving. This eliminates the filename conflict while preserving full per-shard test result reporting.

https://app.circleci.com/agents/gh/DataSQRL/chat/8819afe9-47aa-4b77-9678-bc6c6329b9bd

…e-test

Both parallel nodes produced failsafe-summary.xml, causing CircleCI to fail
both "Uploading test results" steps. Collect only TEST-*.xml files into a
shard-indexed subdirectory before store_test_results to avoid the conflict.

AI-Generated: true
@velo
velo merged commit 676b27a into ci/shard-container-e2e-tests Jul 29, 2026
11 of 14 checks passed
@velo
velo deleted the chunk/fix-container-e2e-duplicate-failsafe-summary branch July 29, 2026 18:12
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.

1 participant