Repository navigation
Open
Labels
P2Normal priority bug or improvement with limited blast radius.Normal priority bug or improvement with limited blast radius.ci: main-flakeTests failing on main, reported by the main failure watchTests failing on main, reported by the main failure watchclawsweeper:current-main-reproClawSweeper found a high-confidence current-main issue reproduction.ClawSweeper found a high-confidence current-main issue reproduction.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.ClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.This issue has meaningful maintainer-visible impact outside the owned taxonomy.issue-rating: 🦀 challenger crabExceptional issue quality: high-confidence current-main reproduction and actionable evidence.Exceptional issue quality: high-confidence current-main reproduction and actionable evidence.
Description
This issue collects test failures on main, one comment per failed CI run attempt. Each comment mentions the authors of the pull requests that last changed the failing tests. Close it when main is green again; the next failure opens a new one.
Run 43999241493, attempt 1 failed on a0a2a24
Failed jobs: Tray UI tests (workspace and chat layout shard), CI Gate
Please check: @bkudiess
| Failed test | Artifact | Last changed in | Pull request | Author |
|---|---|---|---|---|
OpenClaw.Tray.UITests.ReactorChatLayoutProofTests.ConversationParity_ProgrammaticOrComposerFocusRetainsFollowing |
test-results-tray-ui-shard |
243f9cff53d8 | #2093 | @bkudiess |
"Last changed in" is the most recent commit that changed the test method. It is often the cause of a new failure, but it can be a later refactor, and an older test can fail because of a product change. Authors: please check whether your change made this test fail or flaky, then fix forward or propose a revert. This watch never reruns or reverts anything.
Reacted by clawsweeper
Metadata
Metadata
Assignees
Labels
P2Normal priority bug or improvement with limited blast radius.Normal priority bug or improvement with limited blast radius.ci: main-flakeTests failing on main, reported by the main failure watchTests failing on main, reported by the main failure watchclawsweeper:current-main-reproClawSweeper found a high-confidence current-main issue reproduction.ClawSweeper found a high-confidence current-main issue reproduction.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.ClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.This issue has meaningful maintainer-visible impact outside the owned taxonomy.issue-rating: 🦀 challenger crabExceptional issue quality: high-confidence current-main reproduction and actionable evidence.Exceptional issue quality: high-confidence current-main reproduction and actionable evidence.
Type
Fields
Priority
None yet
Projects
- StatusShow more project fieldsBacklog
Activity
clawsweeper commentedon Nov 17, 2026
Codex review: this still needs some work.
Summary
Current main still fails the Tray suite and CI Gate, so this issue has not met its documented close condition.
Reproducibility: GitHub records a failed Tray test step on the exact current-main revision, and the failure watch names three failing settings-publication tests; this review ran no tests and did not inspect their assertion traces.
Next step
Inspect the latest Tray failure traces and suite context to distinguish production concurrency failures from harness interference before choosing a focused repair.
Review details
Best possible solution:
Repair the evidenced failure causes while preserving their assertions, then confirm the affected suite and current-main CI pass.
Do we have a high-confidence way to reproduce the issue?
GitHub records a failed Tray test step on the exact current-main revision, and the failure watch names three failing settings-publication tests; this review ran no tests and did not inspect their assertion traces.
Is this the best way to solve the issue?
Investigate the failing suite before selecting a repair, because current source already releases serialization before notifications and isolated passes would not clear the recorded suite failure.
AGENTS.md: found and applied where relevant.
Remaining risk / open question:
Codex review notes: model internal, reasoning medium; reviewed against 91070a21147a.
Label changes
Label changes:
issue-rating: 🦀 challenger crab: Current issue advisory state selects this label.clawsweeper:current-main-repro: Current issue advisory state selects this label.clawsweeper:no-new-fix-pr: Current issue advisory state selects this label.clawsweeper:needs-maintainer-review: Current issue advisory state selects this label.issue-rating: 🦪 silver shellfish: Current issue advisory state no longer selects this label.Label justifications:
P2: Recurring current-main test failures require investigation without evidence of an urgent shipped-user regression.impact:other: The demonstrated impact is unreliable CI validation and blocked CI Gate.Evidence reviewed
What I checked:
.github/workflows/ci.yml, 91070a21147a)tests/OpenClaw.Tray.Tests/SettingsSandboxPublicationTests.cs:94, 91070a21147a)docs/TEST_COVERAGE.md:722, 91070a21147a)src/OpenClaw.Tray.WinUI/Services/SettingsManager.cs:752, 91070a21147a)scripts/CiMainFailureWatch.ps1:29, 9d6148f642ab)Likely related people:
scripts/CiMainFailureWatch.ps1)How this review workflow works
@clawsweeper re-reviewcomments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.@clawsweeper re-reviewor@clawsweeper re-runon an open PR or issue to request a fresh review only.@clawsweeper reviewto request a fresh review only.@clawsweeper explainto ask for more context, or@clawsweeper stopto stop active automation.Reviewed November 21, 2026, 6:55 PM ET / 23:55 UTC.
3 remaining items
github-actions commentedon Nov 19, 2026
Run 44425756439, attempt 1 failed on 996ac69
Failed jobs:
Mock Gateway application tests (fixture UI shard B),CI GatePlease check: @bkudiess
OpenClaw.Tray.UITests.GatewayFixtureUiTests.MainSearch_MessageHitOpensItsNativeConversationWithoutSendingtest-results-gateway-fixture-shard"Last changed in" is the most recent commit that changed the test method. It is often the cause of a new failure, but it can be a later refactor, and an older test can fail because of a product change. Authors: please check whether your change made this test fail or flaky, then fix forward or propose a revert. This watch never reruns or reverts anything.
github-actions commentedon Nov 19, 2026
Run 44460609847, attempt 1 failed on 8ffe470
Failed jobs:
Mock Gateway application and compatibility tests,CI GatePlease check: @bkudiess
OpenClaw.Tray.UITests.GatewayFixtureUiTests.SessionsDesignNativeWindowGallerytest-results-gateway-fixture"Last changed in" is the most recent commit that changed the test method. It is often the cause of a new failure, but it can be a later refactor, and an older test can fail because of a product change. Authors: please check whether your change made this test fail or flaky, then fix forward or propose a revert. This watch never reruns or reverts anything.
github-actions commentedon Nov 19, 2026
Run 44633226637, attempt 1 failed on e9423ae
Failed jobs:
Tray, setup, and integration tests,CI GatePlease check: @bkudiess
OpenClaw.Tray.Tests.SettingsSandboxPublicationTests.PersistedRevisionControlsAdmissionBeforeSavedObserversFinishtest-results-tray"Last changed in" is the most recent commit that changed the test method. It is often the cause of a new failure, but it can be a later refactor, and an older test can fail because of a product change. Authors: please check whether your change made this test fail or flaky, then fix forward or propose a revert. This watch never reruns or reverts anything.
github-actions commentedon Nov 21, 2026
Run 44961910362, attempt 1 failed on 91070a2
Failed jobs:
Tray, setup, and integration tests,CI GatePlease check: @bkudiess
OpenClaw.Tray.Tests.SettingsSandboxPublicationTests.StoreChangedCallbacksDoNotHoldWriterLockOrLoseConcurrentOriginstest-results-trayOpenClaw.Tray.Tests.SettingsSandboxPublicationTests.SavedCallbacksRunOutsideSettingsSerializationtest-results-trayOpenClaw.Tray.Tests.SettingsSandboxPublicationTests.PersistedRevisionControlsAdmissionBeforeSavedObserversFinishtest-results-tray"Last changed in" is the most recent commit that changed the test method. It is often the cause of a new failure, but it can be a later refactor, and an older test can fail because of a product change. Authors: please check whether your change made this test fail or flaky, then fix forward or propose a revert. This watch never reruns or reverts anything.