[SPARK-46474][INFRA] Upgrade upload-artifact action to v4 #44728
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
This reverts commit c18c87d.
|
The verification of environmental variables is as follows: |
This reverts commit 6f06ba5.
HyukjinKwon
approved these changes
Jan 17, 2024
|
Merged to master. |
|
Let's continue to observe. Additionally, I am trying to fix the |
|
According to the |
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.
What changes were proposed in this pull request?
The pr aims to upgrade upload-artifact action from v3 to v4.
After PR #44698, our environment variable(
PYTHON_TO_TEST) is correctly passed and assigned value.We will bring back this PR: #44662
Why are the changes needed?
v4.0.0 release notes: https://github.com/actions/upload-artifact/releases/tag/v4.0.0
They have numerous performance and behavioral improvements.
v3 VS v4: actions/upload-artifact@v3...v4.0.0
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass GA.
Was this patch authored or co-authored using generative AI tooling?
No.