-
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
[Release][Ruby][CI] Verification job fails for Ruby under conda #44268
Comments
When I pause the job locally and try to run
The referenced shebang looks wrong to me: root@ed232b035d9f:/arrow-tmp# head -n 1 /arrow-tmp/mambaforge/envs/conda-source/bin/glib-mkenums
#!/home/conda/feedstock_root/build_artifacts/glib-split_1727379927883/_build_env/bin/python3.12 I now see that an issue has been filed on glib-feedstock about this. |
I'm trying just pinning the glib version the release verification script uses which makes lets the script continue but now I'm getting an issue during bundling and installing glib2:
|
This is a workaround for the issue reported in apache#44268.
This is a workaround for the issue reported in apache#44268.
The above was just caused by a messy environment inside my container. After deleting $ARROW_TMPDIR, pinning glib works. I created at PR at #44270 which fixes this. Once glib pushes a new release we can unpin our version. |
…n script (#44270) ### Rationale for this change Fixes failing verification task for ruby+conda, see #44268. cc @ raulcd ### What changes are included in this PR? It looks like the proximate cause of the failure was a buggy release of glib (2.82.1) on conda-forge, see conda-forge/glib-feedstock#191. Pinning the version of glib we install inside the verification script to the previous version seems to work (verification passes locally now). Once the glib feedstock pushes a new release with the fix we can unpin this. ### Are these changes tested? Yes, locally under docker. ### Are there any user-facing changes? No. * GitHub Issue: #44268 Lead-authored-by: Bryce Mecum <[email protected]> Co-authored-by: Sutou Kouhei <[email protected]> Signed-off-by: Bryce Mecum <[email protected]>
Issue resolved by pull request 44270 |
…rification script (#44407) ### Rationale for this change We can remove these pins now that conda-forge/glib-feedstock#191 has been closed. I've tested on my own crossbow and will test here momentarily. This effectively reverts #44270 and #44268. ### What changes are included in this PR? Tweaks to release release verification script, specifically removing recently-added pins. ### Are these changes tested? Yes: https://github.com/amoeba/crossbow/actions/runs/11335070956/job/31522511285. ### Are there any user-facing changes? No. Closes #44415. * GitHub Issue: #44415 Authored-by: Bryce Mecum <[email protected]> Signed-off-by: Bryce Mecum <[email protected]>
…rification script (#44407) ### Rationale for this change We can remove these pins now that conda-forge/glib-feedstock#191 has been closed. I've tested on my own crossbow and will test here momentarily. This effectively reverts #44270 and #44268. ### What changes are included in this PR? Tweaks to release release verification script, specifically removing recently-added pins. ### Are these changes tested? Yes: https://github.com/amoeba/crossbow/actions/runs/11335070956/job/31522511285. ### Are there any user-facing changes? No. Closes #44415. * GitHub Issue: #44415 Authored-by: Bryce Mecum <[email protected]> Signed-off-by: Bryce Mecum <[email protected]>
Describe the bug, including details regarding any error messages, version, and platform.
The verification job for Ruby with
USE_CONDA=1
is failing see https://github.com/ursacomputing/crossbow/actions/runs/11092813842/job/30818318871.The specific error is:
I can reproduce this locally with:
Component(s)
Continuous Integration, Release, Ruby
The text was updated successfully, but these errors were encountered: