Skip to content

trunk-merge/pr-1277/a69f58bc-9e84-4ee0-a1a2-1c7876d1afb4 - #1290

Closed
trunk-io[bot] wants to merge 9 commits into
mainfrom
trunk-merge/pr-1277/a69f58bc-9e84-4ee0-a1a2-1c7876d1afb4
Closed

trunk-io[bot] wants to merge 9 commits into
mainfrom
trunk-merge/pr-1277/a69f58bc-9e84-4ee0-a1a2-1c7876d1afb4

Conversation

@trunk-io

@trunk-io trunk-io Bot commented Nov 4, 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 03962cd17da8cc06eea4fda0da9d74e32bdcbe4d.

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 1277, stacked on pull requests 1266 and 1273.

dfrankland and others added 9 commits November 4, 2026 19:50
Leaves stdout free for the command's own output, which the upcoming
`--output-format json` relies on. Logs only show with `--verbose`, so
default output is unchanged.

TRUNK-22400

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
`to_trace_filter` mapped `LevelFilter::Off` to `TRACE`, so the quietest
setting logged the most. Map it to `LevelFilter::OFF` and filter events by
level in the console layer.

TRUNK-22400

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
As `tracing::error!`, each deprecation counted as an error in Sentry even
though nothing failed. Log them with `warn!` and tag them with a
`deprecated_flag` field. Sentry now records warnings with that field as
warning-level events, with the same tags as errors, so we can still see
which customers use deprecated flags. Other warnings stay breadcrumbs.

This also starts reporting `--use-quarantining`, which was already a
`warn!` and so never reached Sentry.

TRUNK-22400

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
TRUNK-22400

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
`run_test` didn't pass its `render_sender` to `run_upload`, so `test`
skipped the slow-request messages that `upload` shows.

TRUNK-22400

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
run() returns a Report, and main sends each part of it to its own stream:
the summary goes to stdout with superconsole's emit_aux, while notices
(deprecation warnings, BEP parse errors), the error of a run that fails
outright, the test command header and the summary file message go to
stderr. DisplayMessage::Final and the EndOutput trait are replaced by
Report and Notice variants that carry the rendered lines.

Scripts that capture only stderr will lose the summary.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
main's #1287 printed Deprecation and UploadSkipped notices inside the upload
summary. This branch already prints every notice on stderr through
render_notices, so render UploadSkipped there and drop the copy in the
summary, which would have printed each notice twice.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
`--output-format json` (or `TRUNK_OUTPUT_FORMAT=json`) prints the summary on
stdout as the same JSON that `--summary-output-file` writes, instead of the
text summary. Logs, notices and progress stay on stderr, and a run that fails
outright prints its JSON error object on stdout. Exit codes don't change.

The flag lives in its own args struct used only by `upload` and `validate`:
`test` includes `UploadArgs`, and its test command writes to stdout.

The summary schema now covers the validate report (`"type": "VALIDATE"`).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@trunk-staging-io

trunk-staging-io Bot commented Nov 4, 2026 •

Copy link
Copy Markdown

Static Badge   Static Badge   Static 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 The quarantine test failed because it expected 2 + 2 to equal 5, but the result was 4. Logs ↗︎

View Full Report ↗︎ ⋅ Docs

@codecov-commenter

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 92.66667% with 11 lines in your changes missing coverage. Please review.
✅ Project coverage is 86.02%. Comparing base (03962cd) to head (c6f8fc2).

Files with missing lines Patch % Lines
cli/src/main.rs 94.17% 6 Missing ⚠️
cli/src/upload_command.rs 50.00% 2 Missing ⚠️
display/src/message.rs 90.90% 2 Missing ⚠️
cli/src/test_command.rs 85.71% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1290      +/-   ##
==========================================
+ Coverage   85.54%   86.02%   +0.48%     
==========================================
  Files          86       85       -1     
  Lines       19405    19395      -10     
==========================================
+ Hits        16600    16685      +85     
+ Misses       2805     2710      -95     

☔ 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 Nov 4, 2026
@trunk-io
trunk-io Bot deleted the trunk-merge/pr-1277/a69f58bc-9e84-4ee0-a1a2-1c7876d1afb4 branch November 4, 2026 20:18
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