Skip to content

Improve software layer scripts workflow - #10

Open
casparvl wants to merge 26 commits into
mainfrom
improve_software_layer_scripts_workflow
Open

Improve software layer scripts workflow#10
casparvl wants to merge 26 commits into
mainfrom
improve_software_layer_scripts_workflow

Conversation

@casparvl

@casparvl casparvl commented Aug 4, 2026

Copy link
Copy Markdown
Owner

No description provided.

Caspar van Leeuwen and others added 26 commits January 13, 2026 16:44
…casparvl/software-layer into improve_software_layer_scripts_workflow
…f this causes the associated CI job to fail
…or the bot/build.sh that gets checked in CI
@casparvl

casparvl commented Aug 4, 2026

Copy link
Copy Markdown
Owner Author

Testing with the bot/software_layer_scripts_commit file.

bot: build repo:eessi.io-2025.06-software instance:eessi-bot-casparvl-aws for:arch=x86_64/amd/zen2

@eessi-bot-casparvl-aws

eessi-bot-casparvl-aws Bot commented Aug 4, 2026

Copy link
Copy Markdown

New job on instance eessi-bot-casparvl-aws for repository eessi.io-2025.06-software
Building on: amd-zen2
Building for: x86_64/amd/zen2
Job dir: /project/def-users/casparvl/eessi-bot-casparvl-aws/jobs/2026.08/pr_10/183326
Commit SHA: 7dc0d7d6389cf024cfe4e1d5a8da49ce4259640a
software-layer-script SHA: 62b8e332fb041a9ba598dbed3ed781a3416407c0

date job status comment
Aug 04 16:23:06 UTC 2026 submitted job id 183326 awaits release by job manager
Aug 04 16:23:36 UTC 2026 released job awaits launch by Slurm scheduler
Aug 04 16:24:39 UTC 2026 running job 183326 is running
Aug 04 16:28:44 UTC 2026 finished
😁 SUCCESS (click triangle for details)
Details
✅ job output file slurm-183326.out
✅ no message matching FATAL:
✅ no message matching ERROR:
✅ no message matching FAILED:
✅ no message matching required modules missing:
✅ found message(s) matching No missing installations
✅ found message matching .tar.* created!
Artefacts
eessi-2025.06-software-linux-x86_64-amd-zen2-17858608570.tar.zstsize: 0 MiB (81456 bytes)
entries: 91
modules under 2025.06/software/linux/x86_64/amd/zen2/modules/all
cowsay/3.04.lua
software under 2025.06/software/linux/x86_64/amd/zen2/software
cowsay/3.04
reprod directories under 2025.06/software/linux/x86_64/amd/zen2/reprod
cowsay/3.04/20260804_162720UTC
other under 2025.06/software/linux/x86_64/amd/zen2
no other files in tarball
Aug 04 16:28:44 UTC 2026 test result
😢 FAILURE (click triangle for details)
Reason
EESSI test suite was not run, test step itself failed to execute.
Details
✅ job output file slurm-183326.out
❌ found message matching ERROR:
✅ no message matching [\s*FAILED\s*].*Ran .* test case

@casparvl

casparvl commented Aug 4, 2026

Copy link
Copy Markdown
Owner Author

bot:status

@eessi-bot-casparvl-aws

Copy link
Copy Markdown

This is the status of all the bot: build commands:

on for repo result commit SHA date status url
amd-zen2 x86_64/amd/zen2 eessi.io-2025.06-software job 183326 is running 7dc0d7d Aug 04 16:24:39 UTC 2026 running #10 (comment)

@casparvl

casparvl commented Aug 4, 2026

Copy link
Copy Markdown
Owner Author

bot:status

@eessi-bot-casparvl-aws

Copy link
Copy Markdown

This is the status of all the bot: build commands:

on for repo result commit SHA date status url
amd-zen2 x86_64/amd/zen2 eessi.io-2025.06-software 😁 SUCCESS 7dc0d7d Aug 04 16:28:44 UTC 2026 finished #10 (comment)

@casparvl

casparvl commented Aug 4, 2026

Copy link
Copy Markdown
Owner Author

Hm, it doesn't list the software-layer-script SHA in the status overview for some reason... Technically speaking, it's not needed either: since the checksum is under version control within the software-layer repo, having the software-layer repo checksum already allows us to figure out which software-layer-scripts commit was used. So maybe I should remove the logic for that configurable file that gets dumped into the report?

@casparvl

casparvl commented Aug 4, 2026

Copy link
Copy Markdown
Owner Author

For posterity: this was done using this version of the build bot casparvl/eessi-bot-software-layer@4d0cf6c

@casparvl

casparvl commented Aug 4, 2026

Copy link
Copy Markdown
Owner Author

Now trying from casparvl/eessi-bot-software-layer@e334ac6

bot: build repo:eessi.io-2025.06-software instance:eessi-bot-casparvl-aws for:arch=x86_64/amd/zen2

@eessi-bot-casparvl-aws

eessi-bot-casparvl-aws Bot commented Aug 4, 2026

Copy link
Copy Markdown

New job on instance eessi-bot-casparvl-aws for repository eessi.io-2025.06-software
Building on: amd-zen2
Building for: x86_64/amd/zen2
Job dir: /project/def-users/casparvl/eessi-bot-casparvl-aws/jobs/2026.08/pr_10/183341
Commit SHA: 7dc0d7d6389cf024cfe4e1d5a8da49ce4259640a

date job status comment
Aug 04 18:00:24 UTC 2026 submitted job id 183341 awaits release by job manager
Aug 04 18:00:53 UTC 2026 released job awaits launch by Slurm scheduler
Aug 04 18:06:03 UTC 2026 running job 183341 is running
Aug 04 18:07:07 UTC 2026 finished
😁 SUCCESS (click triangle for details)
Details
✅ job output file slurm-183341.out
✅ no message matching FATAL:
✅ no message matching ERROR:
✅ no message matching FAILED:
✅ no message matching required modules missing:
✅ found message(s) matching No missing installations
✅ found message matching .tar.* created!
Artefacts
eessi-2025.06-software-linux-x86_64-amd-zen2-17858667880.tar.zstsize: 0 MiB (80952 bytes)
entries: 91
modules under 2025.06/software/linux/x86_64/amd/zen2/modules/all
cowsay/3.04.lua
software under 2025.06/software/linux/x86_64/amd/zen2/software
cowsay/3.04
reprod directories under 2025.06/software/linux/x86_64/amd/zen2/reprod
cowsay/3.04/20260804_180610UTC
other under 2025.06/software/linux/x86_64/amd/zen2
no other files in tarball
Aug 04 18:07:07 UTC 2026 test result
😢 FAILURE (click triangle for details)
Reason
EESSI test suite was not run, test step itself failed to execute.
Details
✅ job output file slurm-183341.out
❌ found message matching ERROR:
✅ no message matching [\s*FAILED\s*].*Ran .* test case

@casparvl

casparvl commented Aug 4, 2026

Copy link
Copy Markdown
Owner Author

Removed backticks from the config, so that this thing becomes a link:

bot: build repo:eessi.io-2025.06-software instance:eessi-bot-casparvl-aws for:arch=x86_64/amd/zen2

@eessi-bot-casparvl-aws

eessi-bot-casparvl-aws Bot commented Aug 4, 2026

Copy link
Copy Markdown

New job on instance eessi-bot-casparvl-aws for repository eessi.io-2025.06-software
Building on: amd-zen2
Building for: x86_64/amd/zen2
Job dir: /project/def-users/casparvl/eessi-bot-casparvl-aws/jobs/2026.08/pr_10/183342
Commit SHA: 7dc0d7d

date job status comment
Aug 04 18:02:42 UTC 2026 submitted job id 183342 awaits release by job manager
Aug 04 18:03:00 UTC 2026 released job awaits launch by Slurm scheduler
Aug 04 18:07:06 UTC 2026 running job 183342 is running
Aug 04 18:11:14 UTC 2026 finished
😁 SUCCESS (click triangle for details)
Details
✅ job output file slurm-183342.out
✅ no message matching FATAL:
✅ no message matching ERROR:
✅ no message matching FAILED:
✅ no message matching required modules missing:
✅ found message(s) matching No missing installations
✅ found message matching .tar.* created!
Artefacts
eessi-2025.06-software-linux-x86_64-amd-zen2-17858670510.tar.zstsize: 0 MiB (81028 bytes)
entries: 91
modules under 2025.06/software/linux/x86_64/amd/zen2/modules/all
cowsay/3.04.lua
software under 2025.06/software/linux/x86_64/amd/zen2/software
cowsay/3.04
reprod directories under 2025.06/software/linux/x86_64/amd/zen2/reprod
cowsay/3.04/20260804_181035UTC
other under 2025.06/software/linux/x86_64/amd/zen2
no other files in tarball
Aug 04 18:11:14 UTC 2026 test result
😢 FAILURE (click triangle for details)
Reason
EESSI test suite was not run, test step itself failed to execute.
Details
✅ job output file slurm-183342.out
❌ found message matching ERROR:
✅ no message matching [\s*FAILED\s*].*Ran .* test case

@casparvl

casparvl commented Aug 4, 2026

Copy link
Copy Markdown
Owner Author

bot:status

@eessi-bot-casparvl-aws

Copy link
Copy Markdown

This is the status of all the bot: build commands:

on for repo result commit SHA date status url
amd-zen2 x86_64/amd/zen2 eessi.io-2025.06-software 😁 SUCCESS 7dc0d7d6389cf024cfe4e1d5a8da49ce4259640a Aug 04 16:28:44 UTC 2026 finished #10 (comment)
amd-zen2 x86_64/amd/zen2 eessi.io-2025.06-software job id 183341 awaits release by job manager 7dc0d7d6389cf024cfe4e1d5a8da49ce4259640a Aug 04 18:00:24 UTC 2026 submitted #10 (comment)
amd-zen2 x86_64/amd/zen2 eessi.io-2025.06-software job id 183342 awaits release by job manager 7dc0d7d Aug 04 18:02:42 UTC 2026 submitted #10 (comment)

@casparvl

casparvl commented Aug 4, 2026

Copy link
Copy Markdown
Owner Author

bot:status last_build

@eessi-bot-casparvl-aws

Copy link
Copy Markdown

This is the status of all the bot: build commands:

on for repo result commit SHA date status url
amd-zen2 x86_64/amd/zen2 eessi.io-2025.06-software 😁 SUCCESS 7dc0d7d6389cf024cfe4e1d5a8da49ce4259640a Aug 04 16:28:44 UTC 2026 finished #10 (comment)

@casparvl

casparvl commented Aug 4, 2026

Copy link
Copy Markdown
Owner Author

Wait a second, it's picking the wrong build as the last build... maybe it's using the wrong column now for sorting? (the one with the commit sha instead of the date)

@casparvl

casparvl commented Aug 4, 2026

Copy link
Copy Markdown
Owner Author

Oh, it's not broken: it shows the last build that had SUCCESS status. The others were still going. That's why. Probably should give me the last build now:

bot:status last_build

@eessi-bot-casparvl-aws

Copy link
Copy Markdown

This is the status of all the bot: build commands:

on for repo result commit SHA date status url
amd-zen2 x86_64/amd/zen2 eessi.io-2025.06-software 😁 SUCCESS 7dc0d7d Aug 04 18:11:14 UTC 2026 finished #10 (comment)

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.

1 participant