Skip to content

run-slot-gauges-lock.test.ts's dead-lock takeover case fails now and then on ubuntu-26.04 #1077

Closed

Description

@nrjdalal

The gauges-lock test "eight looks at a dead lock together each read the stale or the new reading, and leave one well-formed reading and no lock" (tests/scripts/ops/run-slot-gauges-lock.test.ts) fails now and then on Linux: one of the eight looks prints a slot count other than 1 (the stale reading) or 4 (the new one).

Sightings

Ruled out (measured)

  • run-slot gauges lock test flakes: eight looks with no reading run top 6 times #956's mkdir race: the failure above came with GNU's mkdir in the fake.
  • Another uutils tool, at least in isolation: on ubuntu-26.04, mv is GNU 9.7, and rmdir and stat are uutils 0.10.0. A probe ran this case alone 60 times with only mkdir swapped and 60 times with all 104 of the image's gnu* tools first on PATH: 0 bad rounds each time. So it hasn't been reproduced outside the whole file.

What we don't know yet

  • Which value the bad look printed. The assertion reports only false, so a run that fails says nothing about the look: an empty line (the look died), a shut count, or something else.
  • Whether it needs the rest of the file running with it (a leftover look from an earlier case, the load from the one-second fake tops) or just more rounds than 120.

Done when

  • The failing value and its stderr are known. A first step is for the case to report each look's slots and stderr when it fails (toEqual on the list, or a message carrying them).
  • The cause is shown red on the current code and green after the fix, with 20 green runs in a row of the file in ubuntu:26.04.

Activity

  1. added a commit that references this issue on Nov 9, 2026
    c88ae1b
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

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions