Skip to content

{2026.06}[2026.1,riscv64/generic] LLVM 21.1.8 - #1593

Open
bedroge wants to merge 1 commit into
EESSI:mainfrom
bedroge:2026.1_llvm_riscv
Open

{2026.06}[2026.1,riscv64/generic] LLVM 21.1.8#1593
bedroge wants to merge 1 commit into
EESSI:mainfrom
bedroge:2026.1_llvm_riscv

Conversation

@bedroge

@bedroge bedroge commented Aug 28, 2026

Copy link
Copy Markdown
Collaborator

Try to get LLVM 21.1.8 built for RISC-V, as we skipped it in #1583.

@bedroge

bedroge commented Aug 28, 2026

Copy link
Copy Markdown
Collaborator Author

I've tried it interactively on a premier node, but ran out of disk space. These nodes typically have 15-20GB of space available in /tmp. I've temporarily reconfigured the bot to use the arriesgado-jammy partition/node, which has ~200GB available.

bot: build repo:eessi.io-2026.06-software instance:eessi-bot-riscv-prod for:arch=riscv64/generic

@bedroge

bedroge commented Aug 28, 2026

Copy link
Copy Markdown
Collaborator Author

Typo in the config file...

bot: build repo:eessi.io-2026.06-software instance:eessi-bot-riscv-prod for:arch=riscv64/generic

@riscv-eessi-io-bot

riscv-eessi-io-bot Bot commented Aug 28, 2026

Copy link
Copy Markdown

New job on instance eessi-bot-riscv-prod for repository eessi.io-2026.06-software
Building on: generic
Building for: riscv64/generic
Job dir: /home/eessibot/production/shared/jobs/2026.08/pr_1593/322017

date job status comment
Aug 28 14:40:39 UTC 2026 submitted job id 322017 awaits release by job manager
Aug 28 14:41:04 UTC 2026 released job awaits launch by Slurm scheduler
Aug 28 14:42:09 UTC 2026 running job 322017 is running
Aug 28 14:43:11 UTC 2026 finished
😢 FAILURE (click triangle for details)
Details
✅ job output file slurm-322017.out
❌ found message matching FATAL:
❌ found message matching ERROR:
✅ no message matching FAILED:
✅ no message matching required modules missing:
❌ no message matching No missing installations
✅ found message matching .tar.* created!
Artefacts
Details
No artefacts were created or found.
Aug 28 14:43:11 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-322017.out
❌ found message matching ERROR:
✅ no message matching [\s*FAILED\s*].*Ran .* test case

@bedroge

bedroge commented Aug 28, 2026

Copy link
Copy Markdown
Collaborator Author

That didn't work:

INFO:    Starting build...
INFO:    Verifying bootstrap image /var/tmp/eessibot/EESSI/eessi_job.c83txw3Hjd/eessi.nfFBqy6ggK/ghcr.io_eessi_build_node_debian13.sif
WARNING: integrity: signature not found for object group 1
WARNING: Bootstrap image could not be verified, but build will continue.
INFO:    Extracting local image...
ERROR:   unpackSIF failed: root filesystem extraction failed: extract command failed: ESC[91mERROR  : Failed to create container process: Operation not permitted
ESC[0m: exit status 1
FATAL:   While performing build: packer failed to pack: while unpacking local image: root filesystem extraction failed: extract command failed: ESC[91mERROR  : Failed to create contain
er process: Operation not permitted

@bedroge

bedroge commented Aug 28, 2026

Copy link
Copy Markdown
Collaborator Author

Trying it on a pioneer node (which also has a large local disk) instead.

bot: build repo:eessi.io-2026.06-software instance:eessi-bot-riscv-prod for:arch=riscv64/generic

@riscv-eessi-io-bot

riscv-eessi-io-bot Bot commented Aug 28, 2026

Copy link
Copy Markdown

New job on instance eessi-bot-riscv-prod for repository eessi.io-2026.06-software
Building on: generic
Building for: riscv64/generic
Job dir: /home/eessibot/production/shared/jobs/2026.08/pr_1593/322019

date job status comment
Aug 28 14:46:38 UTC 2026 submitted job id 322019 awaits release by job manager
Aug 28 14:47:17 UTC 2026 released job awaits launch by Slurm scheduler
Aug 28 14:48:21 UTC 2026 running job 322019 is running

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