Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@alexarchambault
Copy link
Member

No description provided.

@alexarchambault alexarchambault force-pushed the graalvm-22.3.0 branch 2 times, most recently from d999041 to 109b94e Compare December 21, 2022 17:18
@alexarchambault
Copy link
Member Author

Seems the CI failure needs to be investigated on an actual aarch64 machine...

@tgodzik
Copy link
Collaborator

tgodzik commented Dec 23, 2022

Seems the CI failure needs to be investigated on an actual aarch64 machine...

Would a docker image on M1 machine be a good place to debug? I can take a look next week, I need to anyway install docker on the machine in the office.

@alexarchambault
Copy link
Member Author

alexarchambault commented Dec 23, 2022

@tgodzik A Linux aarch64 VM on any cloud should do. That's what I usually use in such cases. Raspberry pis 4 should also be fine, albeit kind of slow.

@alexarchambault
Copy link
Member Author

alexarchambault commented Jan 20, 2023

I removed the Linux / aarch64 job in #2658. We can always investigate issues in VirtusLab/coursier-m1, where the Linux / aarch64 launchers are now managed.

@lwronski
Copy link
Contributor

I found interesting line in logs. It's seems, that proxy tests using docker, which is not available in docker now.

@alexarchambault
Copy link
Member Author

@lwronski Yeah, it seems it went away. The docker tests are disabled too in VirtusLab/coursier-m1, but could be re-instated (as we generate the Linux launcher there from docker, we'd need to be able to run "docker-in-docker", which needs a bit of setup…)

@alexarchambault alexarchambault merged commit 5533272 into coursier:main Jan 20, 2023
@alexarchambault alexarchambault deleted the graalvm-22.3.0 branch January 20, 2023 17:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants