Quarantine flaky TestKiller Windows CTRL_BREAK subtest

Lachlan Grantrequested to merge
flaky-testkiller-windows-ctrlbreak into main

Summary

TestKiller/command_terminated,_disable_useWindowsLegacyProcessStrategy intermittently fails on Windows integration-test jobs with exit code 0xc000013a (STATUS_CONTROL_C_EXIT) instead of the expected 3.

Root cause: the test sends the helper sleep process a CTRL_BREAK_EVENT after only a fixed time.Sleep(1 * time.Second). On a loaded/slow Windows CI runner there's a race between Go's runtime installing its console-control handler and the event being delivered, so Windows sometimes applies its default termination action before the helper's own handler runs.

This quarantines the subtest the same way its sibling TestKiller/command_terminated_via_job_object is already quarantined, so it stops blocking unrelated merge requests while a proper synchronization fix is investigated.

Closes #39642 (closed)

Evidence

Observed on windows 1809 integration tests 2/4: https://gitlab.com/gitlab-org/gitlab-runner/-/jobs/15609634860 (merge train for !6991 (merged), an unrelated Podman integration-test change)

Test plan

  • .flaky-tests.txt updated with the new entry
  • CI green

Merge request reports