Skip to content

0.1.8 Beta2 CI: determinize recurring Windows Rust lifecycle fixtures #356

Description

@NOirBRight

Problem

Hosted CI run 30904259353 on the exact #62 candidate b712be1021179c9d2415bef631bc8c1c466e0c0d failed Rust debug with two existing Windows lifecycle tests:

  • proxy::tests::inspection_returns_when_a_descendant_inherits_output_handlesGateway process inspection timed out.
  • proxy::tests::restart_after_settings_port_change_stops_recorded_port_before_starting_new_port — Gateway did not become healthy within 20 seconds.

The PR changes are Python/docs/evidence-only; this is an independent Hosted test-fixture regression. The failure is a release blocker and must not be hidden by reruns.

Scope

Acceptance

  • The two focused tests pass 10 consecutive runs in Rust normal and debug flavors.
  • The complete Rust normal/debug matrix and Clippy pass on a new exact candidate without rerunning the failed job.
  • No P0/P1/P2 review finding remains at the exact SHA.
  • The change does not modify Python routing, catalog, tool compatibility, or release behavior.

Relationships

Verification-Class: strict

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1Priority 1: current iteration goalbugSomething isn't workingcampaign:0.1.8-beta20.1.8 Beta2 generic tool compatibility campaignready-for-agentFully specified, ready for an AFK agenttier:heavyOrchestrator provider tier: heavywayfinder:taskWayfinder implementation task

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions