chore(ci): Update older integ job to prep for deprecation#5501
Merged
chore(ci): Update older integ job to prep for deprecation#5501
Conversation
7 tasks
lrstewart
reviewed
Sep 12, 2025
jmayclin
approved these changes
Sep 15, 2025
goatgoose
approved these changes
Sep 16, 2025
lrstewart
approved these changes
Sep 18, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Release Summary:
Resolved issues:
Partial for #5503
Description of changes:
Remove any overlap from nix in the older integrationv2 job, by removing some libcryptos.
Drop the awslc-fips build with gcc4.8 and add it to Openssl-102-FIPS. This gives us coverage of a more realistic build combination.
Call-outs:
This is the first of a couple PRs to speed up and retire some tests.
By dropping all but three libcrypto's and increasing the instance size, the runtime moved from ~50min to ~18min.
Testing:
How is this change tested (unit tests, fuzz tests, etc.)? CI
How can you convince your reviewers that this PR is safe and effective? snapshot results checked in with the nix PR.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.