BF-47023: jstests/noPassthrough/index_builds/index_build_killop_secondary_before_commit.js failed on windows-debug-suggested. Re-disable the test on Windows by adding the incompatible_with_windows_tls tag to get the waterfall green, until the underlying test race is fixed in SERVER-138284 (bug ticket).

Background

The second phase of the test intentionally crashes the secondary via fassert 51101 by sending a killOp after the index build has voted for commit. The test asserts the
killOp command succeeds, but the killOp response races with the crash it triggers. On the CPU-constrained Windows debug host the secondary aborted before the response was flushed, and the shell failed with "Connection closed by peer". See SERVER-138284 (bug ticket) for the full analysis.

History

• SERVER-97380 added the incompatible_with_windows_tls tag in Nov 2024 after BF-34210.
• SERVER-116978 removed the tag in Feb 2026 after fixing the Windows minidump loader-lock issue.
• BF-47023 shows the test is still not Windows-safe, for a different reason than the original ban.

Scope of Work

• Add incompatible_with_windows_tls to the tags of jstests/noPassthrough/index_builds/index_build_killop_secondary_before_commit.js, with a TODO comment pointing at SERVER-138284 (bug ticket).