Skip to content

🤖 tests: phone repro editCancelKeepsDraft once showed an empty composer after Cancel #5810

Description

@ThomasK33

Problem

The bug-bash repro tests/bugbash/repros/editCancelKeepsDraft.e2e.ts failed once on the phone target in CI. The web target passed in the same job. It is an assertion failure, not a timeout:

So after Cancel on a phone-width layout, the composer sometimes shows an empty box instead of the unsent draft. If the user then types or sends, the draft is lost.

Notes

Next step

Run the phone repro in a loop on main and on #5801's head (for example 20 times each) and compare the failure counts.


Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high

Activity

  1. ThomasK33 commented on Oct 8, 2026

    @ThomasK33
    MemberAuthor

    Second occurrence, first reported as #5876. Same test, same phone target, same assertion.

    Two occurrences in about 10 days, both on phone, both after Cancel. Still not reproduced locally (an earlier 20-run loop passed 20/20 on main). The cause is still open: a real intermittent draft loss at phone width, or a timing gap between toBeHidden and the value check. The planned fix for #5672 and #5571 (replacing #5801) must run this repro in a loop on its branch and on main and report both counts.


    Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high

  2. ThomasK33 commented on Oct 9, 2026

    @ThomasK33
    MemberAuthor

    Another sighting, this time on the web target.

  3. ThomasK33 commented on Oct 10, 2026

    @ThomasK33
    MemberAuthor

    Third sighting, again on web. This time it removed a PR from the merge queue.

    • Merge-group run 38082874892, Test / E2E (linux 1/4) (job 114303270432), commit 449fbe9846 (main ea19a44101 plus 🤖 tests: bug-bash sandbox runtime fixes from the readiness reviews (D1) #6082). 🤖 tests: bug-bash sandbox runtime fixes from the readiness reviews (D1) #6082 changes only tests/bugbash/sandbox/** and docs.
    • Same assertion: editCancelKeepsDraft.e2e.ts:28, composer "" instead of unsent draft. The failed attempt took 6.53 s. Passing runs take about 2.2 s, and the phone target in the same job passed in 1.87 s.
    • Local check on 449fbe9846 with the mock app AI and --retries 0: 16 of 16 passed. 10 were the repro alone on web, and 6 were the whole web repro phase in CI order.
    • The job uploads no e2e artifacts, and trace: on-first-retry records nothing with retries 0. So no sighting so far left a trace or screen. The next step is a trace on CI, for example trace: 'retain-on-failure' for the repro phase, so the next failure shows its state.

    The coordinator desk owns this issue now.


    Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high

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

    flakeinvestigationTriage: proposal / research / tracking

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions