Summary

burn_in schedules with_mongot_extension_ suite tasks on general variants (e.g. enterprise-amazon-linux2023-arm64-all-feature-flags-required-query-patch-only, the -generated-by-burn-in-tags variants) that lack the mongot-integration setup steps. Since SERVER-130648 made these suites load the real (signed) mongot-extension, those tasks can no longer start: every shard mongod fasserts at startup with Failed to verify extension signature (11528920 → fassert 126502), all fixture_setup_0 steps fail, and no tests run.

The same tasks on the mongot-integration variants are green on the same base commit, so this is purely a task-generation gap: burn_in should not schedule these suites on variants that can't stage the real extension (or those variants need the same extension staging steps).

Impact

Every patch touching a test in the with_mongot_extension_* suites (anything under jstests/with_mongot/e2e/**) gets red burn_in tasks on required variants.

Evidence

• Failing: patch 6a51351cdda4f700079550f8 (jstests-only diff, base a0c1947cac6) — all burn_in:with_mongot_extension_* tasks fail fixture setup.
• Passing (same base, same diff): patch 6a5137d3e9fc2c00077a0a06 — with_mongot_extension_* on amazon2023-arm64-mongot-integration-patchable all green.
• Regression window: burn_in extension tasks still started their fixtures on base 6a6101eaf21 (pre-SERVER-130648).

Related: SERVER-130648, SERVER-130914, SERVER-131029 (where this surfaced).