-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
None
-
Correctness
-
Fully Compatible
-
ALL
-
v8.0, v7.3, v7.0, v6.0, v5.0
- name: .concurrency !.no_txns !.repl !.kill_terminate
The changes from 542d00d as part of SERVER-39414 had subtly define the concurrency_replication_ubsan, concurrency_replication_causal_consistency_ubsan, concurrency_replication_multi_stmt_txn_ubsan to not have the "repl" Evergreen task tag. The changes from f83d51c as part of SERVER-50710 unknowingly added the "repl" Evergreen task tag to these definitions and caused the UBSan DEBUG build variant to stop running these tasks.
The concurrency_replication_ubsan, concurrency_replication_causal_consistency_ubsan, concurrency_replication_multi_stmt_txn_ubsan tasks were always meant to be temporary. They were first introduced in July 2018 as part of SERVER-35964. However there appeared to be a memory pressure issue which was never investigated. The more recent changes from 38a98af as part of SERVER-35964 removed the Evergreen task definitions and resmoke YAML suite files because they appeared unused.
We should restore the MongoDB 4.4 coverage. We can consider either reintroducing the Evergreen task definitions and resmoke YAML suite files or updating the Evergreen task selector for the build variant.
- is caused by
-
SERVER-50710 Lock acquired in FindCmd run() method is not yielded by SBE
- Closed
- is related to
-
SERVER-35964 Delete UBSan concurrency_replication* tasks
- Closed
-
SERVER-86530 Make evergreen validate have zero lint warnings for etc/evergreen.yml and etc/evergreen_nightly.yml
- Investigating
-
SERVER-39414 Use task tags in evergreen.yml
- Closed