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 65 build variants
Also ensures a good cross-section of tests in PRs for coverage.
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, or any of the other non-standard tests.
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.
Ensure that sync and async tasks run the appropriate tests for all task families
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, covering the new suite-identity, sync/async-split, and matrix-size invariants.
New tests pass in Evergreen: XXXX Patch URL
Checklist for Author
Did you update the changelog (if necessary)? (CI-only change.)
Is there test coverage?
Is any followup work tracked in a JIRA ticket? If so, add link(s). N/A
Checklist for Reviewer
Does the title of the PR reference a JIRA Ticket?
Do you fully understand the implementation? (Would you be comfortable explaining how this code works to someone else?)
Is all relevant documentation (README or docstring) updated?
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.
The reason will be displayed to describe this comment to others. Learn more.
🔵 Needs a closer look
The broad Evergreen matrix and platform-specific OpenSSL/environment changes depend on an unavailable submodule and placeholder patch, while static generator tests cannot verify cross-platform task selection or end-to-end execution, requiring human Evergreen validation.
The reason will be displayed to describe this comment to others. Learn more.
🔵 Needs a closer look
Human assessment is needed because the configuration change may remove the baseline Linux standard test matrix, creating a potentially critical gap in the generated build variants.
The reason will be displayed to describe this comment to others. Learn more.
🟡 Changes recommended
Active moderate and critical findings remain: the rhel8 OCSP variant is not included in PR builds, and default-family tasks no longer filter to the default test suite.
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.
PYTHON-6167
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.Also ensures a good cross-section of tests in PRs for coverage.
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, or any of the other non-standard tests.
Changes
test-non-standardwith one family per suite; a task's name identifies its suite, and distro tags decide which variant runs it.drivers-evergreen-toolssubmodule.Testing
python3 -m pytest .evergreen/scripts/test_generate_config.pypasses, covering the new suite-identity, sync/async-split, and matrix-size invariants.Checklist for Author
Checklist for Reviewer