-
Notifications
You must be signed in to change notification settings - Fork 728
Add renegotiate apache test to nix/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
base: main
Are you sure you want to change the base?
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.
export PYTEST_ARGS="--provider-version $S2N_LIBCRYPTO -x -n auto --reruns=2 --durations=10 -rpfs --cache-clear --ignore-glob=*test_dynamic_record_sizes* --ignore-glob=*test_session_resumption*" | ||
uvinteg_snapshot |
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'm not sure the two excluded tests are obvious enough :/ I'm worried someone looking at the buildspec will think we now have parity between nix and the job that still uses codebuild images, and remove the codebuild image job.
And what's the benefit of this PR? It looks like nix used to be able to run test_session_resumption, but can't anymore?
function integ {(set -e | ||
apache2_start |
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.
It seems wrong for uvinteg
to start apache, but integ
not to anymore. If the integ target doesn't work anymore, shouldn't we just remove it / replace it?
Release Summary:
Resolved issues:
partial for #5040
Description of changes:
Start apache2 with the
uvinteg
bash function, allowing this test to pass with nix+uv+pytest.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.