-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
Labels:None
-
Fully Compatible
-
ALL
-
STM 2020-08-24
When burn_in_tests are generated, the suites resmoke args are returned by the burn-in tests API call and can be duplicated in the resmoke command line invocation. For example, when the following test:
"name": "burn_in:noPassthrough_1_enterprise-rhel-62-64-bit-resumable-index-builds",
"commands": [
{
"func": "do setup"
},
{
"func": "run tests",
"vars": {
"resmoke_args": "--suites=no_passthrough --storageEngine=wiredTiger --mongodSetParameters=\"{enableResumableIndexBuilds: true}\" --excludeWithAnyTags=resumable_index_build_incompatible --repeatTestsSecs=600 --repeatTestsMin=2 --repeatTestsMax=1000 jstests/noPassthrough/resumable_index_build_drain_writes_phase_primary.js"
}
}
],
is run in the resumable index builds buildvariant, the "enableResumableIndexBuilds: true" gets added once for the variant, and once from the API response.
Given this, it's not obvious whether variants should be including burn-in tests (assuming the enterprise rhel 6.2 builder is expected to be the canonical runner of burn-in tests).
However, it's a simple enough change to have resmoke cope with identical key/value pairs until the burn-in tests behavior is better understood.
- is related to
-
-
- Closed
-