Flaky Evidence test: normalized runtime startup sees Transit unavailable under CI load

Open Beginner friendly
#2,698 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
75/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
testing

Research direction

Start with crates/registry-evidence/src/normalized_tests.rs, especially the fixture and startup sequence around line 1296; check how the Unix-socket Transit fake accepts connections and how attemptTimeoutMilliseconds is configured. Run the named test repeatedly under parallel load. Done means the test waits for the fake to accept a connection and uses a deadline that remains reliable under runner load.

Written by the indexing model from the issue text.

Description

normalized_tests::normalized_authority_without_profile_actor_retains_definition_actor_ceiling in crates/registry-evidence failed once in the Rust tests (evidence) job and passed when the job was re-run. It also passes five times in a row locally.

The panic is at crates/registry-evidence/src/normalized_tests.rs:1296:

normalized runtime initializes: Signing(Transit(Unavailable))

At startup the runtime probes the signing key through the test's Unix-socket Transit fake. Unavailable means that request failed to send or hit its timeout. The fixture sets attemptTimeoutMilliseconds: 2000, so the likely cause is the fake answering too slowly while the test job runs at full parallelism. This matches earlier fixed-deadline flakes under CI load.

The pull request that hit it does not change registry-evidence or registry-platform-crypto.

Done when the fixture's Transit probe cannot fail on runner load. For example, wait for the fake to accept a connection before startup and give the test a deadline that load cannot reach.

Dominant language
Rust
Stars
2
Forks
0
Avg merge
9h 48m
Merged PRs (30d)
151

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from registrystack/registry-stack

All issues in registrystack/registry-stack

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.