Skip to content

Tests failing on main (tracking) #2262

Open

Description

@github-actions

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.

Activity

  1. added
    clawsweeper:intake:bugPreliminary submission classification; full source review pending.
    clawsweeper:intake:needs-reproPreliminary submission classification; full source review pending.
    P2Normal priority bug or improvement with limited blast radius.
    clawsweeper:needs-maintainer-reviewClawSweeper 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.
    impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.
    issue-rating: 🦪 silver shellfishThin issue quality; more reproduction proof or environment detail is needed.
    and removed
    clawsweeper:intake:bugPreliminary submission classification; full source review pending.
    clawsweeper:intake:needs-reproPreliminary submission classification; full source review pending.
    on Nov 17, 2026
  2. clawsweeper commented on Nov 17, 2026

    @clawsweeper

    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:

    • The latest assertion traces remain uninspected, so a product concurrency defect cannot yet be distinguished from test scheduling or suite interference.
    • Earlier UI failures and the current settings-publication failures do not establish one shared root cause.

    Codex review notes: model internal, reasoning medium; reviewed against 91070a21147a.

    Label changes

    Label changes:

    • add issue-rating: 🦀 challenger crab: Current issue advisory state selects this label.
    • add clawsweeper:current-main-repro: Current issue advisory state selects this label.
    • add clawsweeper:no-new-fix-pr: Current issue advisory state selects this label.
    • add clawsweeper:needs-maintainer-review: Current issue advisory state selects this label.
    • remove 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:

    Likely related people:

    • Barbara Kudiess: Raw commit 9d6148f adds scripts/CiMainFailureWatch.ps1:29 relative to its recorded parents. This identifies author metadata, not feature responsibility or a PR merger. (role: source-line author; confidence: high; commits: 9d6148f642ab; files: scripts/CiMainFailureWatch.ps1)
    How this review workflow works
    • ClawSweeper keeps one durable marker-backed review comment per issue or PR.
    • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
    • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
    • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
    • Maintainers can also comment @clawsweeper review to request a fresh review only.
    • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge; those execution lanes are retired.
    • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

    Reviewed November 21, 2026, 6:55 PM ET / 23:55 UTC.

  3. 3 remaining items

  4. github-actions commented on Nov 19, 2026

    @github-actions
    ContributorAuthor

    Run 44425756439, attempt 1 failed on 996ac69

    Failed jobs: Mock Gateway application tests (fixture UI shard B), CI Gate

    Please check: @bkudiess

    Failed test Artifact Last changed in Pull request Author
    OpenClaw.Tray.UITests.GatewayFixtureUiTests.MainSearch_MessageHitOpensItsNativeConversationWithoutSending test-results-gateway-fixture-shard 4ea07e858b81 #2016 @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.

  5. removed
    clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.
    clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.
    on Nov 19, 2026
  6. github-actions commented on Nov 19, 2026

    @github-actions
    ContributorAuthor

    Run 44460609847, attempt 1 failed on 8ffe470

    Failed jobs: Mock Gateway application and compatibility tests, CI Gate

    Please check: @bkudiess

    Failed test Artifact Last changed in Pull request Author
    OpenClaw.Tray.UITests.GatewayFixtureUiTests.SessionsDesignNativeWindowGallery test-results-gateway-fixture 7de197bb3c0c #2329 @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.

  7. added
    clawsweeper:needs-maintainer-reviewClawSweeper 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.
    on Nov 19, 2026
  8. github-actions commented on Nov 19, 2026

    @github-actions
    ContributorAuthor

    Run 44633226637, attempt 1 failed on e9423ae

    Failed jobs: Tray, setup, and integration tests, CI Gate

    Please check: @bkudiess

    Failed test Artifact Last changed in Pull request Author
    OpenClaw.Tray.Tests.SettingsSandboxPublicationTests.PersistedRevisionControlsAdmissionBeforeSavedObserversFinish test-results-tray 932bc0e3c7b7 #2028 @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.

  9. removed
    clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.
    clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.
    on Nov 20, 2026
  10. github-actions commented on Nov 21, 2026

    @github-actions
    ContributorAuthor

    Run 44961910362, attempt 1 failed on 91070a2

    Failed jobs: Tray, setup, and integration tests, CI Gate

    Please check: @bkudiess

    Failed test Artifact Last changed in Pull request Author
    OpenClaw.Tray.Tests.SettingsSandboxPublicationTests.StoreChangedCallbacksDoNotHoldWriterLockOrLoseConcurrentOrigins test-results-tray 932bc0e3c7b7 #2028 @bkudiess
    OpenClaw.Tray.Tests.SettingsSandboxPublicationTests.SavedCallbacksRunOutsideSettingsSerialization test-results-tray 932bc0e3c7b7 #2028 @bkudiess
    OpenClaw.Tray.Tests.SettingsSandboxPublicationTests.PersistedRevisionControlsAdmissionBeforeSavedObserversFinish test-results-tray 932bc0e3c7b7 #2028 @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.

  11. added
    clawsweeper:current-main-reproClawSweeper found a high-confidence current-main issue reproduction.
    clawsweeper:needs-maintainer-reviewClawSweeper 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.
    issue-rating: 🦀 challenger crabExceptional issue quality: high-confidence current-main reproduction and actionable evidence.
    and removed
    issue-rating: 🦪 silver shellfishThin issue quality; more reproduction proof or environment detail is needed.
    on Nov 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal priority bug or improvement with limited blast radius.ci: main-flakeTests failing on main, reported by the main failure watchclawsweeper:current-main-reproClawSweeper found a high-confidence current-main issue reproduction.clawsweeper:needs-maintainer-reviewClawSweeper 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.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.issue-rating: 🦀 challenger crabExceptional issue quality: high-confidence current-main reproduction and actionable evidence.

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions