From this patch: https://spruce.corp.mongodb.com/task/mongodb_mongo_master_linux_64_debug_required_display_burn_in_tests_patch_d08338397b1423a558330418e0c1697083b40e43_6a7350e51da6d10007cb3fd1_26_08_05_15_04_37/execution-tasks?execution=0&sorts=STATUS%3AASC

2 tasks fail with:

Error: No test results found for target '//jstests/suites/cluster-scalability:sharded_collections_jscore_passthrough_with_config_shard_burn_in_jstests_core_sharding_query_cbr_shard_filter_limit.js' in 'src/build_events.json'.

Claude says that this is a negation bug in the burn-in target selection, where the tag filter for the variant is (link):

resmoke_tests_tag_filter: ci-development-critical,ci-release-critical,-suggested_excluding_required__for_devprod_mitigation_only,-requires_all_feature_flags,-requires_compile_variant,-incompatible_development_variant

The two suites have ci-release-critical and suggested_excluding_required__for_devprod_mitigation_only  (link and link), which means the negation should exclude them (which happens in resmoke).

Claude claims that the way this is done in bazel_burn_in.py here is wrong because each negated entry becomes attr(tags, '\b-suggested_excluding_required…'), where - is a regex literal, so it matches nothing and the exclusion is dropped.