There are some jscore timeseries tests (timeseries_create.js) that insert uncompressed buckets directly into the system.bucket.* collection, which can cause the collection validation hook to fail in shard merge passthrough suites on feature flags build variant. That's because we run the validate command with enforceTimeseriesBucketsAreAlwaysCompressed set to true when featureFlagTimeseriesAlwaysUseCompressedBuckets is enabled.

timeseries_reopened_bucket_insert.js, which also inserts uncompressed buckets directly into the system.bucket.* collection, faced a similar BF issue. But, we fixed the problem by tagging the test as tenant_migration_incompatible. I don't think that's a correct way to fix this problem.

Those problematic tests not only does uncompressed bucket testing but also perform compressed bucket testing. Thus, blacklisting those tests would result in a loss of coverage for those compressed bucket testing in the merge passthrough suites. So, I recommend running the merge passthrough suites with skipEnforceTimeseriesBucketsAreAlwaysCompressedOnValidate. Once featureFlagTimeseriesAlwaysUseCompressedBuckets is enabled by default by defauly(targeted for 7.3), I anticipate that PM-3055 will update all jscore tests to remove explicit uncompressed bucket sequence testing.

This is problem also applies to tenant migration and shard split passthrough suites