-
Notifications
You must be signed in to change notification settings - Fork 2
0.1.8 Beta2 CI: determinize recurring Windows Rust lifecycle fixtures #356
Copy link
Copy link
Closed
Labels
P1Priority 1: current iteration goalPriority 1: current iteration goalbugSomething isn't workingSomething isn't workingcampaign:0.1.8-beta20.1.8 Beta2 generic tool compatibility campaign0.1.8 Beta2 generic tool compatibility campaignready-for-agentFully specified, ready for an AFK agentFully specified, ready for an AFK agenttier:heavyOrchestrator provider tier: heavyOrchestrator provider tier: heavywayfinder:taskWayfinder implementation taskWayfinder implementation task
Description
Metadata
Metadata
Assignees
Labels
P1Priority 1: current iteration goalPriority 1: current iteration goalbugSomething isn't workingSomething isn't workingcampaign:0.1.8-beta20.1.8 Beta2 generic tool compatibility campaign0.1.8 Beta2 generic tool compatibility campaignready-for-agentFully specified, ready for an AFK agentFully specified, ready for an AFK agenttier:heavyOrchestrator provider tier: heavyOrchestrator provider tier: heavywayfinder:taskWayfinder implementation taskWayfinder implementation task
Problem
Hosted CI run 30904259353 on the exact #62 candidate
b712be1021179c9d2415bef631bc8c1c466e0c0dfailed Rust debug with two existing Windows lifecycle tests:proxy::tests::inspection_returns_when_a_descendant_inherits_output_handles—Gateway 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
Relationships
Verification-Class: strict