You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
PYTHON-6167 Split the test-non-standard task family into per-suite task families - #3131
Splits the shared test-non-standard Evergreen task family into one family per suite, so a task's name and tags identify the suite it runs. The encryption and load balancer matrices now run as separate sync and async tasks.
Before: 1325 tasks across 76 build variants
After: 833 tasks across 63 build variants
Motivation
The test-non-standard family was shared by the encryption, load balancer, doctest, and PyOpenSSL suites, and only the build variant decided which suite a task actually ran. That made failures hard to attribute.
Additionally, we were not testing sync and async separately for encryption or load balancer, and we were only testing load balancer with its own marker. The load balancer tests are meant to run the whole suite.
Changes
Replaces test-non-standard with one family per suite; a task's name identifies its suite, and distro tags decide which variant runs it.
Selects the sync or async half of a suite from a SYNC environment variable.
Builds OpenSSL 3 on RHEL 8 so free-threaded PyOpenSSL cells can run there, using the updated drivers-evergreen-tools submodule.
Testing
python3 -m pytest .evergreen/scripts/test_generate_config.py passes (21 tests), covering the new suite-identity, sync/async-split, and matrix-size invariants.
The reason will be displayed to describe this comment to others. Learn more.
🔵 Needs a closer look
Three moderate review findings remain unresolved in task generation and configuration.
No open issues 🎉
1 previously missed issue
In code that hasn't changed since last review
Allowlist TEST_CRYPT_SHARED for crypt_shared test tasks
.evergreen/scripts/generate_config.py:1615
The crypt_shared tasks now put TEST_CRYPT_SHARED in the run tests command vars, but the environment allowlist still omits it. setup_tests.py reads this value to enable the crypt_shared setup, so the new crypt_shared tasks will run without that configuration and test the regular libmongocrypt path instead. Add TEST_CRYPT_SHARED to this allowlist.
# Double quotes expand `$` and backticks: keep the value literal.
value = value.replace("$", "\\$").replace("`", "\\`")
This branch has not been deployed
No deployments
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Splits the shared
test-non-standardEvergreen task family into one family per suite, so a task's name and tags identify the suite it runs. The encryption and load balancer matrices now run as separate sync and async tasks.Motivation
The
test-non-standardfamily was shared by the encryption, load balancer, doctest, and PyOpenSSL suites, and only the build variant decided which suite a task actually ran. That made failures hard to attribute.Additionally, we were not testing sync and async separately for encryption or load balancer, and we were only testing load balancer with its own marker. The load balancer tests are meant to run the whole suite.
Changes
test-non-standardwith one family per suite; a task's name identifies its suite, and distro tags decide which variant runs it.SYNCenvironment variable.drivers-evergreen-toolssubmodule.Testing
python3 -m pytest .evergreen/scripts/test_generate_config.pypasses (21 tests), covering the new suite-identity, sync/async-split, and matrix-size invariants.