-
Notifications
You must be signed in to change notification settings - Fork 28.1k
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
[SPARK-35413][INFRA] Use the SHA of the latest commit when checking out databricks/tpcds-kit #32561
Conversation
Kubernetes integration test starting |
Kubernetes integration test status failure |
Test build #138586 has finished for PR 32561 at commit
|
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.
Seems like a fine idea. How often does this change? do we risk not picking up important changes? but yeah we should pin this.
Good idea to prevent unexpected changes in the future while we may have a risk not to pick up the important change. |
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.
+1, LGTM.
Thank you, @srowen @kiszk @dongjoon-hyun I re-triggered a job to generate the data for checking if it works correctly before merging this. |
Yea, I think the change rarely happens, but as its better to avoid unexpected test failures as much as possible. |
This reverts commit c1184ee.
Kubernetes integration test starting |
Kubernetes integration test status failure |
…ut databricks/tpcds-kit ### What changes were proposed in this pull request? This PR proposes to use the SHA of the latest commit ([2a5078a782192ddb6efbcead8de9973d6ab4f069](databricks/tpcds-kit@2a5078a)) when checking out `databricks/tpcds-kit`. This can prevent the test workflow from breaking accidentally if the repository changes drastically. ### Why are the changes needed? For better test workflow. ### Does this PR introduce _any_ user-facing change? No, dev-only. ### How was this patch tested? GA passed. Closes #32561 from maropu/UseRefInCheckout. Authored-by: Takeshi Yamamuro <[email protected]> Signed-off-by: Takeshi Yamamuro <[email protected]> (cherry picked from commit 2390b9d) Signed-off-by: Takeshi Yamamuro <[email protected]>
…ut databricks/tpcds-kit ### What changes were proposed in this pull request? This PR proposes to use the SHA of the latest commit ([2a5078a782192ddb6efbcead8de9973d6ab4f069](databricks/tpcds-kit@2a5078a)) when checking out `databricks/tpcds-kit`. This can prevent the test workflow from breaking accidentally if the repository changes drastically. ### Why are the changes needed? For better test workflow. ### Does this PR introduce _any_ user-facing change? No, dev-only. ### How was this patch tested? GA passed. Closes #32561 from maropu/UseRefInCheckout. Authored-by: Takeshi Yamamuro <[email protected]> Signed-off-by: Takeshi Yamamuro <[email protected]> (cherry picked from commit 2390b9d) Signed-off-by: Takeshi Yamamuro <[email protected]>
okay, I've checked if it works correctly. Merged to master/3.0/3.1. |
Thank you, @HyukjinKwon , too. |
Test build #138594 has finished for PR 32561 at commit
|
…ut databricks/tpcds-kit ### What changes were proposed in this pull request? This PR proposes to use the SHA of the latest commit ([2a5078a782192ddb6efbcead8de9973d6ab4f069](databricks/tpcds-kit@2a5078a)) when checking out `databricks/tpcds-kit`. This can prevent the test workflow from breaking accidentally if the repository changes drastically. ### Why are the changes needed? For better test workflow. ### Does this PR introduce _any_ user-facing change? No, dev-only. ### How was this patch tested? GA passed. Closes apache#32561 from maropu/UseRefInCheckout. Authored-by: Takeshi Yamamuro <[email protected]> Signed-off-by: Takeshi Yamamuro <[email protected]> (cherry picked from commit 2390b9d) Signed-off-by: Takeshi Yamamuro <[email protected]>
What changes were proposed in this pull request?
This PR proposes to use the SHA of the latest commit (2a5078a782192ddb6efbcead8de9973d6ab4f069) when checking out
databricks/tpcds-kit
. This can prevent the test workflow from breaking accidentally if the repository changes drastically.Why are the changes needed?
For better test workflow.
Does this PR introduce any user-facing change?
No, dev-only.
How was this patch tested?
GA passed.