Skip to content

test: TestRunSurvivesARingWaitEBUSY884/submit-and-wait-timeout fails its apparatus guard in Coverage's -race -covermode=atomic build (9 of ~264 runs) #1107

Closed

Description

@FumingPower3925

TestRunSurvivesARingWaitEBUSY884/submit-and-wait-timeout (internal/engine/iouring) fails its own apparatus guard in the Coverage workflow's -race -covermode=atomic build: 9 failures in about 264 Coverage runs that reached the io_uring step (3 of them on main: runs 39068951624, 39334596754, 39460416507), never in the Unit workflow.

Mechanism (reproduced): the arm's 32 unpaced clients keep the loop so busy that it never takes the timed wait the arm exists to exercise, so the test's own guard fires. With a race plus atomic-cover build, one worker, --cpus 4 and no spinners it fails 31 of 40 locally. The clients should pause after each answer in the timed arm; with a 20 ms pause it is 0 of 200 at --cpus 4 (95% upper bound 1.5%) and the full test passes 30 of 30 at --cpus 1 with 3 spinners and 60 of 60 at --cpus 2 with 2 spinners.

Fix: celeris draft PR #1106 (test-only; Refs #N only). Found while triaging the CI flakes of #890 and PR #1105's attempt 1.

Activity

  1. added this to the v1.6.0 milestone on Oct 25, 2026
  2. FumingPower3925 commented on Oct 29, 2026

    @FumingPower3925
    ContributorAuthor

    Fixed by #1106 (merged 2026-10-25), verified by failing-first reproduction in the review of the flake lane: the fix reverted fails the regression test 20 of 20, the merged tree passes 20 of 20 (#1068 epoll async closing response truncation: product bug; #1107 and #1108: test bugs). No recurrence in the CI runs since the merge. Refs #1106.

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

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions