-
Notifications
You must be signed in to change notification settings - Fork 50
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
{2023.06}[foss/2023a] gmsh v4.12.2, basemap v1.39, geopandas v0.14.2 #736
Conversation
Instance
|
Instance
|
bot: build repo:eessi.io-2023.06-software arch:aarch64/generic |
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen2 |
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
I'm confused... it fails with an FLTK download error. But... if I do |
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen2 |
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
It doesn't work on the login node either:
edit: tried a few more AWS node, and I get the same thing on all of them, while it works fine on non-AWS nodes. Maybe it's related to fltk/fltk#976, and they banned AWS IPs? |
I've manually downloaded and copied the source tarball to the bot account, so let's try again. bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen2 |
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
bot: build repo:eessi.io-2023.06-software arch:aarch64/generic |
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
Updates by the bot instance
|
New job on instance
|
The changes in c9613e7 should fix the problem with creating the tarball. @casparvl We should also update |
I think the build step will still report as 'failed'. But I guess at least the tarball will be created correctly. So if you're bold enough to deploy even when the bot calls the build step 'failed', we're good ;-) |
bot: build repo:eessi.io-2023.06-software arch:x86_64/generic |
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
no wait, that's not true. The check-build is done before testing, so those failures are not in the logs yet. Ok, we should be good then :) I'll create a fix for the other issue. |
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
…#736, the test step should be skipped.
Label |
@casparvl Just a single rebuild was good enough, since So I've merged one staging PR, I'll close the others... |
PR merged! Moved |
PR merged! Moved |
PR merged! Moved |
Lol, so true. I got confused since I initially had trouble replicated the issue on an x86_64 platform. But that wasn't because the Oh well, problem solved :D |
No description provided.