Skip to content

trunk-merge/pr-1201/484c16fc-ae39-4516-b8bc-59ef177e6cc0 - #1202

Closed
trunk-io[bot] wants to merge 4 commits into
mainfrom
trunk-merge/pr-1201/484c16fc-ae39-4516-b8bc-59ef177e6cc0
Closed

trunk-io[bot] wants to merge 4 commits into
mainfrom
trunk-merge/pr-1201/484c16fc-ae39-4516-b8bc-59ef177e6cc0

Conversation

@trunk-io

@trunk-io trunk-io Bot commented Sep 16, 2026

Copy link
Copy Markdown
Trunk Merge Pull Request Banner

This pull request was created and is being managed by Trunk Merge.

This pull request is based on the main branch at SHA 3da768f9bc2849059eb08551171b9fd2976902a0.

See more details here.

When CI completes, this pull request will be closed automatically.

Pull Requests Being Tested

This pull request is testing the changes from pull request 1201.

dfrankland and others added 4 commits September 14, 2026 21:36
The argument took literal filenames, so a repository with more than one test
target had to spell out every file `swift test --xunit-output` wrote, and a
pattern reached `File::open` verbatim and failed. `--junit-paths` has always
globbed, so the same spelling meant different things depending on which
argument carried it.

Expansion now goes through the junit path's own, which also brings its
dedupe: matches are keyed by canonical path, so a file two patterns both
match -- or one reached through a symlink as well as directly -- is parsed
once instead of uploading every test it holds twice.

`collect_files_per_glob` took junit wrappers to read one field off each, so
it now takes the globs themselves and `expand_globs` exposes the flattened
result. One implementation, rather than a second one that drifts.

Two consequences worth knowing. A relative value now resolves against the
repo root rather than the working directory, which is what `--junit-paths`
has always done and only differs when the uploader runs outside the repo. And
a value naming a file that is not there no longer fails on open -- it matches
nothing, exactly as a junit glob does, leaving the existing empty-results
check to decide whether that is an error.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
They only exercise `FileSetBuilder::expand_globs`, which is public, so
nothing about them needs to sit inside the module. As an integration test
they exercise the crate the way its callers do and cannot quietly come to
depend on a private detail.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Say what the code does and drop the rest: which argument historically
expanded differently, why a test needs no toolchain, what an uploaded
duplicate would look like downstream.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@trunk-staging-io

trunk-staging-io Bot commented Sep 16, 2026

Copy link
Copy Markdown

Static BadgeStatic BadgeStatic Badge

Failed Test Failure Summary Logs
pending_quarantine_test should be quarantined when run with variant A test marked as pending was expected to fail but unexpectedly passed. Logs ↗︎
variant_quarantine_test should be quarantined when run with variant A test expected the sum of 2 + 2 to be 5, but it was actually 4, indicating a failing assertion. Logs ↗︎

View Full Report ↗︎Docs

@codecov-commenter

codecov-commenter commented Sep 16, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 92.30769% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 83.93%. Comparing base (3da768f) to head (74d0ea8).

Files with missing lines Patch % Lines
cli/src/context.rs 71.42% 2 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1202      +/-   ##
==========================================
+ Coverage   83.70%   83.93%   +0.22%     
==========================================
  Files          74       74              
  Lines       17652    17667      +15     
==========================================
+ Hits        14776    14828      +52     
+ Misses       2876     2839      -37     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@trunk-io trunk-io Bot closed this Sep 16, 2026
@trunk-io
trunk-io Bot deleted the trunk-merge/pr-1201/484c16fc-ae39-4516-b8bc-59ef177e6cc0 branch September 16, 2026 17:20
@trunk-io

trunk-io Bot commented Sep 16, 2026

Copy link
Copy Markdown
Author

Static BadgeStatic BadgeStatic Badge

View Full Report ↗︎Docs

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants