Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Java][CI] Source Verification Java Linux Conda on AMD64 Latest fails #44277

Closed
vibhatha opened this issue Oct 1, 2024 · 6 comments
Closed

[Java][CI] Source Verification Java Linux Conda on AMD64 Latest fails #44277

vibhatha opened this issue Oct 1, 2024 · 6 comments
Assignees
@pitrou
Labels
Component: Continuous Integration Type: bug
Milestone
18.0.0

Comments

@vibhatha
Copy link
Collaborator

vibhatha commented Oct 1, 2024

Describe the bug, including details regarding any error messages, version, and platform.

It seems that the CI verify-rc-source-java-linux-conda-latest-amd64 , has been consistently failing when we run the crossbows. The release verification fails each time.

Component(s)

Java
@vibhatha
Copy link
Collaborator Author

vibhatha commented Oct 1, 2024

cc @lidavidm

@vibhatha
Copy link
Collaborator Author

vibhatha commented Oct 1, 2024

@raulcd has this been observed already in the pre-release events?

@amoeba
Copy link
Member

amoeba commented Oct 1, 2024

I can reproduce this locally in a container and it produces just as little output as the crossbow log does.

Looking at this bit,

2024-10-01T02:37:19.1534699Z ##[warning]Future Miniforge releases will NOT build Mambaforge installers. We advise you switch to Miniforge at your earliest convenience. More details at https://conda-forge.org/news/2024/07/29/sunsetting-mambaforge/.
2024-10-01T02:37:19.1545889Z ERROR: executing pre_install.sh failed

pre_install.sh looks like a conda/mambaforge thing so it seems like that's what's failing and not the verification itself. I looked at the deprecation URL they link to and notice we're just at the edge between the window where the installer will wait for 30s before proceeding and the October first brownout window of 2024-10-01 where installs will fail.

Is it possible the failure is related to the deprecation of mambaforge and that the fix is to switch to miniforge as they indicate?

@vibhatha
Copy link
Collaborator Author

vibhatha commented Oct 1, 2024

Right, probably it could be. Need to look into this I haven't come across this kind of an error before.

@amoeba
Copy link
Member

amoeba commented Oct 1, 2024

I posted on Zulip too: https://ursalabs.zulipchat.com/#narrow/stream/180245-dev/topic/Mambaforge.20deprecation.2C.20brownouts.20start.20Oct.202024.

pitrou added a commit to pitrou/arrow that referenced this issue Oct 1, 2024
@pitrou
apacheGH-44277: [CI] Use Miniforge instead of Mambaforge
4f775e7 
Mambaforge is being deprecated upstream in favor of Miniforge:
https://conda-forge.org/news/2024/07/29/sunsetting-mambaforge/
@github-actions github-actions bot mentioned this issue Oct 1, 2024
Merged
raulcd pushed a commit that referenced this issue Oct 1, 2024
@pitrou
GH-44277: [CI] Use Miniforge instead of Mambaforge (#44278)
6863f50 
Mambaforge is being deprecated upstream in favor of Miniforge: https://conda-forge.org/news/2024/07/29/sunsetting-mambaforge/

* GitHub Issue: #44277

Authored-by: Antoine Pitrou <[email protected]>
Signed-off-by: Raúl Cumplido <[email protected]>
@raulcd raulcd added this to the 18.0.0 milestone Oct 1, 2024
@raulcd
Copy link
Member

raulcd commented Oct 1, 2024

Issue resolved by pull request 44278
#44278

@raulcd raulcd closed this as completed Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pitrou pitrou

Labels
Component: Continuous Integration Type: bug
Projects
None yet
Milestone
18.0.0
Development

No branches or pull requests
4 participants
@amoeba @raulcd @pitrou @vibhatha