chore: Modify tparse check #5425
Merged
+16
−8
Conversation
This file contains 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
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.
Someone ran into a case where a unit test run failed due to not having
tparseeven though the cache restore was successful.https://github.com/hashicorp/boundary/actions/runs/12642066509/job/35225823802
We previously addressed a similar issue with this PR, but in that instance, the cache failed to restore.
I haven't been able to find the root cause. Prior to the failing job, this job was the most recent run that used this cache key -- in this case, that job created the cache and ran the tests successfully. I'm not sure how
tparseended up missing.In any event, this PR modifies the workflow to check if
tparseexists regardless if it restores from the cache successfully.https://hashicorp.atlassian.net/browse/ICU-16152