-
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
WIP: [Release] Verify release-14.0.0-rc2 #38343
Conversation
@github-actions crossbow submit --group verify-rc-source --param release=14.0.0 --param rc=2 |
Revision: 2dcee3f Submitted crossbow builds: ursacomputing/crossbow @ actions-59980692f0 |
Revision: 2dcee3f Submitted crossbow builds: ursacomputing/crossbow @ release-14.0.0-rc2-0 |
@ursabot please benchmark |
Benchmark runs are scheduled for commit 2dcee3f. Watch https://buildkite.com/apache-arrow and https://conbench.ursa.dev for updates. A comment will be posted here when the runs are complete. |
Thanks for your patience. Conbench analyzed the 6 benchmarking runs that have been run so far on PR commit 2dcee3f. There were 2 benchmark results indicating a performance regression:
The full Conbench report has more details. |
@github-actions crossbow submit --group verify-rc-binaries --group verify-rc-wheels --param release=14.0.0 --param rc=2 |
Revision: 2dcee3f Submitted crossbow builds: ursacomputing/crossbow @ actions-ab9d709f3b |
@kou @kszucs any idea why it might be taking more than 6 hours to install system dependencies for
vs the old:
All jobs are successful except that one. I am thinking on sending the vote email nevertheless as both:
where successful with the wheels and the current failure is timing out installing system dependencies, nothing to do verifying the wheels. |
I am surprised as installing system dependencies takes a reasonable amount of time both on macos12-amd64 and macos11-arm64 (10-15 minutes) |
Nonetheless, it looks like a build issue rather than an issue with the release itself. The wheel builds should execute the tests, so I think it is totally fine to not block the vote on this build error. We should be able to verify them locally until the verification builds are fixed. |
Looking at the rest of the builds there are test errors in the go source verification tasks. cc @zeroshade |
Thanks @kszucs the go verification issue has been fixed. Is an issue in the verification script! |
I agree with kszucs. It's not a blocker. |
PR to verify Release Candidate