Skip to content

Contract CI traversal test uses a flaky hosted wall-clock latency threshold #481

Description

@khaliqgant

What happened

A rerun of Relayfile PR #479's Contract workflow failed a different existing test:

--- FAIL: TestPullRemoteFullTreePrunesNestedMountRuntimeBeforeDescendantEnumeration
representative Slack traversal exceeded bounded latency: 794.47377ms across 3 delayed calls

Hosted evidence: https://github.com/AgentWorkforce/relayfile/actions/runs/34275836317/job/102229884832

The test passed functionally and observed only three delayed calls, but failed because a busy hosted runner exceeded its wall-clock limit.

Why this matters

The test intends to prove pruning bounds remote work. A process wall-clock threshold also measures runner scheduling/load, producing nondeterministic required CI without proving a stronger product invariant.

Done when

  • Replace or isolate the wall-clock assertion with deterministic delayed-call/work-bound evidence, or add a scheduling margin that cannot hide an extra remote traversal.
  • Demonstrate the old failure mode and the repaired invariant.
  • Stress the focused test and keep the full Contract workflow green.

Activity

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions