-
Notifications
You must be signed in to change notification settings - Fork 10
feat(e2e-prewarm): pin the SDK version instead of always tracking latest (ROCMAI-430) #464
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
Open
+221
−19
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
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.
MMDDYYYYstill never matches here.normalize_requested_build_date(apps/rocm/src/therock.rs:3742) acceptsYYYY-MM-DD,YYYYMMDDandMMDDYYYY, and there's a test using theMMDDYYYYspelling attherock.rs:8519. Stripping non-digits preserves order, so that form can't line up with theYYYYMMDDrun the key carries. Running the function:So a CI author who copies the
MMDDYYYYspelling fromrocm install sdkgetsDecision::Installon every run — the same multi-GiB re-download this PR fixed, reached by a different spelling.Either canonicalise the pin to
YYYYMMDDbefore comparing (same branchnormalize_requested_build_dateuses: check whether the first or the last four digits start with20), or reject anything but the advertisedYYYY-MM-DDat the flag so the unsupported spellings fail loudly instead of silently re-downloading.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.
Fixed in bdc482e — the pin is canonicalized to YYYYMMDD before comparing (reorders an MMDDYYYY spelling the same way
normalize_requested_build_datedoes), so both spellings now match. Covered bybuild_date_pin_matches_regardless_of_mmddyyyy_or_yyyymmdd_spelling.