burn_in_tests did not detect changes in core

I recently caused a failure due to a new test in the core suite not working in the sharded_collections_jscore_passthrough suite, even though I ran burn_in_tests in a patch build. I felt like burn_in_tests should have caught this.