-
Notifications
You must be signed in to change notification settings - Fork 64
{2023.06}[foss/2023b] Flux 0.76.0 #1107
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
base: main
Are you sure you want to change the base?
Conversation
Instance
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws arch:x86_64/amd/zen2 |
Updates by the bot instance
|
New job on instance
|
New job on instance
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws arch:x86_64/amd/zen2 |
Updates by the bot instance
|
New job on instance
|
New job on instance
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws arch:x86_64/amd/zen2 |
Updates by the bot instance
|
New job on instance
|
New job on instance
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws arch:x86_64/amd/zen2 |
Updates by the bot instance
|
New job on instance
|
New job on instance
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws arch:x86_64/amd/zen2 |
Updates by the bot instance
|
New job on instance
|
New job on instance
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws arch:x86_64/amd/zen2 |
Updates by the bot instance
|
New job on instance
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws arch:x86_64/intel/sapphirerapids |
New job on instance
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws arch:x86_64/intel/sapphirerapids |
New job on instance
|
Tried to build in a container via EESSI-extend, but the build crashed for Flux itself with
Anyone seen this before? |
bot: status last_build |
I'm pretty sure I wasn't ever building docs, it may have found something in your environment that triggered that (maybe it found sphinx?). |
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=x86_64/intel/sapphirerapids |
1 similar comment
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=x86_64/intel/sapphirerapids |
smee forwarder was not running for AWS bot, probably happened by accident when restarting bot after updating it to v0.9.0 (was done this morning) |
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=x86_64/intel/sapphirerapids |
1 similar comment
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=x86_64/intel/sapphirerapids |
New job on instance
|
# and passes for every architecture except sapphaire rapids. Building | ||
# interactively on that arch with EESSI-extend does work so we just | ||
# ignore test failures to get this build ingested. | ||
ignore-test-failure: True |
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.
While this is indeed being picked up, I'm not sure it will have the desired effect as I don't know if it will get passed through to the extensions, I guess we will find out...
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.
If we're talking Python packages as extensions, it should.
install_extension
in PythonPackage
easyblock calls _test_step
(not test_step
), which corresponds to the EasyBlock._test_step
method which takes into account the ignore_test_failure
build option
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.
Since this only applies to Sapphire Rapids, I'm wondering if we should do this more selectively in the EasyBuild hooks instead, but maybe it's not really worth the effort...
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 should have said components not extensions
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.
Ah, indeed, in Bundle
easyblock we're calling comp.test_step
, we should be calling comp._test_step
to make it aware of ignore_test_failure
.
And may we should reconsider the naming in EasyBlock
, so calling out to test_step
ensures that ignore_test_failure
is taken into account...
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
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
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
No description provided.