-
Notifications
You must be signed in to change notification settings - Fork 742
Flip Nix integration tests to use uv/pytest #5352
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: James Mayclin <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think the PR name is accurate. You're not adding the renegotiate apache to nix, and you're not just adding it to uv, you're switching all the nix tests over to uv.
@@ -0,0 +1,22 @@ | |||
<Module test_buffered_send.py> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to confirm, this level of snapshotting is at the test level, and not the case level, right?
So we'd fail if we stopped running test_early_data
, but we won't fail if we just dropped one of the test_early_data
cases?
I guess this would be nasty to track across CI configurations 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct; the case level was attempted in #5266, but it's significantly more complex.
Release Summary:
Resolved issues:
resolves #5040
Description of changes:
Removes the nix shell function
integ
and replaces it withuvinteg
, also eliminating calling out individual integration tests in a list.To mitigate for missing tests, this PR also adds in a snapshot check using pytest's
--collect-only
flag, comparing a list of expected tests with what pytest sees and failing if they don't match. Here is a branch, without the renegotiate_apache test in the snapshot list, failing.Call-outs:
This adds a cleanup routine for apache2 configs, so when doing local runs of the integration tests, the apache2 configs get regenerated. This is not needed in CI, as we're throwing away Docker containers after the test runs.
Testing:
How is this change tested (unit tests, fuzz tests, etc.)? Local, CI.
How can you convince your reviewers that this PR is safe and effective?
Is this a refactor change? If so, how have you proved that the intended behavior hasn't changed?
Remember:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.