Repository navigation
ci(test_reds): read display-named Swift Testing reds and a zero-width-space suite end (port from main) - #35892
Conversation
…o-width-space suite end Both read wrong on feat-cmux-next's copy, which the landers run for every base; main already has the fixes (#35723, #35609). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Agent-Session: https://cmux.com/deeplink/agent?id=aid-8707001042ea634e8771
… zero-width space Ports main's #35723 and #35609 to feat-cmux-next's copy, the canonical base-red classifier the landers run for every base, so main's copy can be the same bytes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Agent-Session: https://cmux.com/deeplink/agent?id=aid-8707001042ea634e8771
|
cmux status (one comment, edited in place; each line is updated by the job that owns it) Review App of this head (app.zip, kept 1 day)
Shipped in:
|
|
Owned by an agent session · session |
|
Review (codex, router-review): SHIP at 4b079b4 Reviewer: codex gpt-6-astra high, fast tier. Follow-ups: 1. They land as checklist items in this PR's one follow-up tracking issue in this repo ( SHIP at 4b079b4 Visual verdict: unchanged by this diff Focused test suites pass (117, 194, and 8 tests).
Follow-ups:
|
…run's reds, and a rate limit exiting 1 Review findings on #35893 (F1, F2). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Agent-Session: https://cmux.com/deeplink/agent?id=aid-8707001042ea634e8771
…ate-limited read A ci-status check-run can stay failed after its job was re-run green; the run was then rescanned and its child reds could be excused. Check the exact job's conclusion for run rollups as for routed ones. Where the evidence reader raises RateLimited (main's), exit 3 so gh-merge-green reports a rate limit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Agent-Session: https://cmux.com/deeplink/agent?id=aid-8707001042ea634e8771
Bugbot needs on-demand usage enabledBugbot uses usage-based billing for this team and requires on-demand usage to be enabled. A team admin can enable on-demand usage in the Cursor dashboard. |
…ed; exit 3 on a rate limit Review findings F1 and F2. The classifier stays feat-cmux-next's bytes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Agent-Session: https://cmux.com/deeplink/agent?id=aid-8707001042ea634e8771
|
Review (codex, router-review): SHIP at 113b580 Reviewer: codex gpt-6.1-sol xhigh, fast tier. Follow-ups: 3. They land as checklist items in this PR's one follow-up tracking issue in this repo ( SHIP at 113b580 Visual verdict: no images; Leo tries the build
Follow-ups:
|
… and an older red listed before a newer green Review findings on #35893. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Agent-Session: https://cmux.com/deeplink/agent?id=aid-8707001042ea634e8771
… them; a pull_request_target run is never base evidence Review findings on #35893 (F1, F2). main's older copy excluded both PR events. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Agent-Session: https://cmux.com/deeplink/agent?id=aid-8707001042ea634e8771
Bugbot needs on-demand usage enabledBugbot uses usage-based billing for this team and requires on-demand usage to be enabled. A team admin can enable on-demand usage in the Cursor dashboard. |
…t_target is never base evidence Review findings. The classifier stays feat-cmux-next's bytes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Agent-Session: https://cmux.com/deeplink/agent?id=aid-8707001042ea634e8771
|
Review (codex, router-review): SHIP at f183487 Reviewer: codex gpt-6.1-sol xhigh, fast tier. Follow-ups: 2. They land as checklist items in this PR's one follow-up tracking issue in this repo ( SHIP at f183487 Visual verdict: unchanged by this diff Targeted classifier and base-red tests pass.
Follow-ups:
|
Summary
feat-cmux-next's
scripts/ci/test_reds.pyis the base-red classifier copy the landers run for every base. main fixed two Swift Testing parsing bugs in its own copy (#35723, #35609) that never reached this one:@Test("A capped plan …")prints✘ Test "A capped plan …" recorded an issue, with no(). The pattern needed the parentheses, so a job whose only reds were display-named tests had no failing tests and was compared by its error lines instead.✔ Suite "x" passed, so a passing suite read as cut short.This ports both, with main's tests. It also fixes two review findings from #35893, which brings main to this copy:
ci-status) whose check-run stayed failed after its job was re-run green: the run was rescanned and its child reds could be excused. The exact job's conclusion is now checked for run rollups too, as it already was for routed ones.RateLimited(main'smain_fix_evidence.py), the classifier exits 3, which gh-merge-green reports as a rate limit. This copy's reader has no such class, so nothing changes here. After it lands, main can carry this file byte for byte (the main PR adds a parity check).Testing
python3 tests/test_test_reds.py: on the base, the two new tests fail (test_display_named_swift_testing_reds_are_compared_by_name,test_a_suite_end_after_a_zero_width_space_is_whole); on the head, 117 tests pass.tests/test_base_red_excuse.py: the two new tests (test_a_red_ci_status_check_whose_job_was_retried_green_blocks,test_a_rate_limited_read_exits_3) fail on the test-only commit and pass at the head (196).tests/test_base_red_excuse.pyandtests/test_ci_guard_check_isolation.pyalso pass.Observed / Not run
Observed: the commands above, red on the test-only commit and green at the head.
Not run: no live PR re-judged with this copy.
Changelog
none
Agent session: agent session
🤖 Generated with Claude Code