test installing EasyBuild v3.8.2 to software.eessi.io/versions/2023.06#29
test installing EasyBuild v3.8.2 to software.eessi.io/versions/2023.06#29boegel wants to merge 31 commits into2023.06-software.eessi.iofrom
software.eessi.io/versions/2023.06#29Conversation
Allow fix incorrect generic path
remove bot configuration (main)
…oftware.eessi.io/versions/2023.06
…d v4.8.2 installations
…2023.06-software.eessi.io_TEST_BOEGEL
…e.eessi.io_TEST_BOEGEL
…-software.eessi.io_TEST_BOEGEL
…o 2023.06-software.eessi.io_TEST_BOEGEL
|
Instance
|
|
bot: build |
Updates by the bot instance
|
|
bot: build |
Updates by the bot instance
|
|
New job on instance
|
|
New job on instance
|
|
Failed with: That likely has to do with switching to edit: fixed in EESSI#397 |
Allow `archdetect` to print all possible cpu paths + fix paths for `aarch64/*` (drop `/arm/` subdir)
…pported currently in software.eessi.io
…heck for directories in software-layer if it has been populated already
…6-software.eessi.io_TEST_BOEGEL
|
bot: build |
Updates by the bot instance
|
|
New job on instance
|
|
New job on instance
|
|
bot: deploy |
Updates by the bot instance
|
|
2nd deploy attempt failed because |
|
3rd deploy attempt failed because |
|
last (4th) deploy attempt triggered successfully, only failed due to lack of credentials, which is a problem with the bot environment, not with the code: What matters is that it used the current bucket from the following spec in bucket_name = {
"eessi-hpc.org-2023.06-compat": "eessi-staging-2023.06",
"eessi-hpc.org-2023.06-software": "eessi-staging-2023.06",
"eessi.io-2023.06-compat": "software.eessi.io-2023.06",
"eessi.io-2023.06-software": "kh-eessi-staging" } |
Using this for testing:
EESSI/software-layer, see overview in: