-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
GH-37936: [CI] Fix integration testing in rc-verify nightly builds #37933
Conversation
pitrou
commented
Sep 28, 2023
•
edited by github-actions
bot
Loading
edited by github-actions
bot
- Closes: [CI] Fix integration testing in rc-verify nightly builds #37936
Thanks for opening a pull request! If this is not a minor PR. Could you open an issue for this pull request on GitHub? https://github.com/apache/arrow/issues/new/choose Opening GitHub issues ahead of time contributes to the Openness of the Apache Arrow project. Then could you also rename the pull request title in the following format?
or
In the case of PARQUET issues on JIRA the title also supports:
See also: |
@github-actions crossbow submit -g verify-rc-source |
This comment was marked as outdated.
This comment was marked as outdated.
3986702
to
73351bb
Compare
@github-actions crossbow submit -g verify-rc-source |
This comment was marked as outdated.
This comment was marked as outdated.
@github-actions crossbow submit verify-rc-source-integration-macos* |
This comment was marked as outdated.
This comment was marked as outdated.
@github-actions crossbow submit verify-rc-source-integration-macos* |
This comment was marked as outdated.
This comment was marked as outdated.
@github-actions crossbow submit verify-rc-source-integration* |
Revision: 758cf86 Submitted crossbow builds: ursacomputing/crossbow @ actions-4e7dde6d23 |
Unfortunately the verify-rc scripts are so slow and so unstable that it's difficult to get a clear idea of successes and failures. @kou Are you able to review this? |
I see a lot of spurious "permission denied" at the end of the macOS arm64 integration build (otherwise successful): |
In general, these changes look good. But there are some failures. For example: verify-rc-source-integration-linux-almalinux-8-amd64 https://github.com/ursacomputing/crossbow/actions/runs/6341261220/job/17224514818#step:6:584
I can help fixing remaining failures in the next week. |
I noticed that one, but I have no idea what the actual issue is, and whether it's related to these changes. |
@pitrou @kou Starting with go-1.18, go will attempt to stamp version control information in any binary that is built with the go toolchain. I'm guessing that the config setting up the env isn't maintaining the |
758cf86
to
42f2f3f
Compare
@github-actions crossbow submit verify-rc-source-integration* |
Ok, I think I have fixed the Go issue (it works locally), but we'll have to wait a couple hours for the Crossbow results now. |
Revision: 42f2f3f Submitted crossbow builds: ursacomputing/crossbow @ actions-51aa7dd70b |
@github-actions crossbow submit -g verify-rc-source |
Revision: 42f2f3f Submitted crossbow builds: ursacomputing/crossbow @ actions-1118476133 |
I'm sorry, but I think it's pointless to wait for all those integration tasks that are failing for unrelated reasons. I will merge this CI, as it does make things better anyway. |
After merging your PR, Conbench analyzed the 5 benchmarking runs that have been run so far on merge-commit 832511a. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 8 possible false positives for unstable benchmarks that are known to sometimes produce them. |
…lds (apache#37933) * Closes: apache#37936 Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Antoine Pitrou <antoine@python.org>
…lds (apache#37933) * Closes: apache#37936 Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Antoine Pitrou <antoine@python.org>
…lds (apache#37933) * Closes: apache#37936 Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Antoine Pitrou <antoine@python.org>