-
Notifications
You must be signed in to change notification settings - Fork 26
EESSI compatibility layer for next version (2025.06) #209
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
Merged
Merged
Changes from all commits
Commits
Show all changes
56 commits
Select commit
Hold shift + click to select a range
ae506ec
use latest bootstrap script
bedroge 8cbb4cb
bump version to 2025.01
bedroge ea89f5e
bump version to 2025.01, stick to GCC 11, use latest gentoo commit, r…
bedroge 257242e
use python 3.12
bedroge 472ac83
log ansible output
bedroge 635837c
add comment about commit, stick to GCC 14 for now
bedroge 727bd47
don't enable stable prefix for x86_64
bedroge b84779a
remove dev-util/hermes
bedroge 27b9ff8
overlay configuration template
bedroge 30324be
add overlay with predefined config files
bedroge d836262
add comment to top of file
bedroge 6b73f53
add spaces to comments
bedroge ab80d43
hardcode eessi_version to 2025.01 for now
bedroge c18fede
use 2025.01_set branch of fork
bedroge 6562419
add reframe test that runs pip check
bedroge 2018d36
disable eselect repository list step
bedroge 5bebdd8
add space
bedroge 0539b1b
hardcode version to 2025.01 for now
bedroge 930abba
look for ld.bfd instead of ld.gold
bedroge 842ae7b
sync with main
bedroge 92b6192
try to run reframe tests with bot
bedroge b9feeeb
script for testing the compat layer with reframe
bedroge 072f77d
use test_compatibility.sh, hardcode version number for now
bedroge 6000ed3
use SLURM_JOB_ID instead of SLURM_JOBID
bedroge 4540dba
get eessi_version from work dir
bedroge 73e7b8c
get eessi_version from tmp dir
bedroge 9f4464d
just find any tarball
bedroge 41a9e41
remove typo
bedroge cd3f7be
set eessi_version after eessi_tmp has been set
bedroge 3dcc415
bump commit to most recent commit (Feb 13), which includes recent Lmo…
bedroge 1df7ff7
Merge branch 'main' into 2025.01
bedroge c1486b6
Merge branch 'main' into 2025.01
bedroge d2462c3
restore removed line
bedroge 979cc6b
Merge branch 'main' of github.com:EESSI/compatibility-layer into 2025.01
bedroge 0b67029
bump eessi_version to 2025.02
bedroge b1d9ce8
use Debian Sid for RISC-V
bedroge 94abb1c
use GCC 13.x by masking >=14
bedroge a87842a
Merge branch 'main' of github.com:EESSI/compatibility-layer into 2025.01
bedroge 0fa499c
use trixie container for RISC-V
bedroge 36a4f34
use different container for testing on RISC-V
bedroge c507e40
add override,nvidia,amd subdirs to glibc trusted dirs
bedroge 781c753
bump version to 2025.06
bedroge 5b68104
use latest bootstrap script
bedroge 611f529
use latest gentoo commit
bedroge 91dab0a
dont use gold linker anymore
bedroge 0e1d56b
Merge branch 'main' of github.com:EESSI/compatibility-layer into 2025.01
bedroge c4d54e8
use Debian 13 container for RISC-V
bedroge 3ed97db
stick to Python 3.13
bedroge 32d47cd
use gentoo commit that includes lmod 8.7.60
bedroge 1ea267b
use Debian 13 container for RISC-V
bedroge 1c3955c
run container with --cleanenv
bedroge fd85d85
clean up
bedroge 7a95394
package set PR has been merged, so use EESSI/gentoo-overlay main branch
bedroge 0828e85
debian-13 instead of debian13 in image name
bedroge e13a842
use debian-13 instead of debian13 in container image name
bedroge 732c317
debian-11 instead of debian11
bedroge File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Does order matter here? Is the first entry in this list also the first one that's considered (so it is effectively the "override" path)?
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.
They are passed in that order to glibc (https://github.com/EESSI/compatibility-layer/blob/main/ansible/playbooks/roles/compatibility_layer/tasks/set_glibc_trusted_dirs.yml#L16), so I would hope/expect that the order matters, but I'll see if I can check that once the build has successfully completed.
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.
Also see #218,