-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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-44461: [Release][Packacing][Python] Set PARQUET_TEST_DATA on verify-release-candidate-wheels.bat #44462
Conversation
|
@github-actions crossbow submit verify-rc-binaries-wheels-windows --param release=18.0.0 --param rc=0 |
Revision: 6ba7a5a Submitted crossbow builds: ursacomputing/crossbow @ actions-f980a8883a
|
The error has been fixed but there seems to be a new error with ORC and Timezones :( :
|
@github-actions crossbow submit verify-rc-binaries-wheels-windows --param release=18.0.0 --param rc=0 |
Revision: 95b3016 Submitted crossbow builds: ursacomputing/crossbow @ actions-5687ee222c
|
@rem Download IANA Timezone Database for ORC C++ | ||
curl https://cygwin.osuosl.org/noarch/release/tzdata/tzdata-2024a-1.tar.xz --output tzdata.tar.xz || exit /B | ||
mkdir %USERPROFILE%\Downloads\test\tzdata | ||
arc unarchive tzdata.tar.xz %USERPROFILE%\Downloads\test\tzdata |
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.
arc does not seem to be present:
'arc' is not recognized as an internal or external command,
operable program or batch file.
There's some more work to be done here :(
@github-actions crossbow submit verify-rc-binaries-wheels-windows --param release=18.0.0 --param rc=0 |
This comment was marked as outdated.
This comment was marked as outdated.
@github-actions crossbow submit verify-rc-binaries-wheels-windows --param release=18.0.0 --param rc=0 |
This comment was marked as outdated.
This comment was marked as outdated.
@github-actions crossbow submit verify-rc-binaries-wheels-windows --param release=18.0.0 --param rc=0 |
Revision: d43d971 Submitted crossbow builds: ursacomputing/crossbow @ actions-2851110c41
|
@github-actions crossbow submit verify-rc-binaries-wheels-windows --param release=18.0.0 --param rc=0 |
Revision: acf0493 Submitted crossbow builds: ursacomputing/crossbow @ actions-628dc0a01d
|
@github-actions crossbow submit verify-rc-binaries-wheels-windows --param release=18.0.0 --param rc=0 |
Revision: 6c3e4a5 Submitted crossbow builds: ursacomputing/crossbow @ actions-c2ac566e6f
|
@github-actions crossbow submit verify-rc-binaries-wheels-windows --param release=18.0.0 --param rc=0 |
Revision: a753b3b Submitted crossbow builds: ursacomputing/crossbow @ actions-55cf78c3ae
|
@github-actions crossbow submit verify-rc-binaries-wheels-windows --param release=18.0.0 --param rc=0 |
It seems that we need to update bundled datetime... |
… verify-release-candidate-wheels.bat
…for nightly wheels verification
@github-actions crossbow submit verify-rc-binaries-wheels-windows --param release=18.0.0 --param rc=0 |
Revision: 7200add Submitted crossbow builds: ursacomputing/crossbow @ actions-2790dff4a5
|
oh! yeah! I'm not sure why I run that, the change won't be there :) |
Yes. I did the same mistake. GH-44482 isn't included in 18.0.0 RC0. So this is still failing. But the |
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.
I am 👍 with merging this, just a small question
@@ -29,6 +29,7 @@ jobs: | |||
{{ key }}: {{ value }} | |||
{% endfor %} | |||
{% endif %} | |||
timeout-minutes: 60 |
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.
I am not against setting the timeout, any specific reason to add it? Those jobs only run on verifying binaries at the moment and it would be unfortunate to start hitting the timeout there
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.
Some jobs such as https://github.com/ursacomputing/crossbow/actions/runs/11393132955/job/31700762815 got stuck when I was working on this. I canceled them manually because we don't have the timeout.
I think that we should have a reasonable timeout to avoid wasting CI time (even when we don't pay money for it). If "60" isn't enough, we can use more long time such as "120". It's better than the default "360".
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.
ok, I went back to historic runs and the longest seems to be 52 minutes:
https://github.com/ursacomputing/crossbow/actions/runs/8704336160/usage
Others:
https://github.com/ursacomputing/crossbow/actions/runs/7507682263/usage
https://github.com/ursacomputing/crossbow/actions/runs/9837997876/usage
Probably 60 is good enough
After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit 1b40800. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 5 possible false positives for unstable benchmarks that are known to sometimes produce them. |
Rationale for this change
The Windows wheel verification fails due to missing
PARQUET_TEST_DATA
What changes are included in this PR?
Add
PARQUET_TEST_DATA
toverify-release-candidate-wheels.bat
which is only tested on the binary verification job.Are these changes tested?
Via archery
Are there any user-facing changes?
No