EESSI 2023.06 compat layer w/ OpenSSL 1.1.1 + GCC 10.4.0 (without using gcc-config)

[boegel]

This PR builds on top of the changes proposed in #184, #185, #186, joint work with @trz42 .

Complete overview of changes:

• EESSI pilot version bumped to 2023.06;
• mask >=dev-libs/openssl-3, so we get OpenSSL 1.1.1 in compat layer (to avoid problems with Rust, Python, Perl);
• only mask >=sys-devel/gcc-11, so we get latest GCC 10.x (10.4.0) as system compiler in compat layer (since GCC 9.x seems to be no longer actively maintained in Gentoo);
• stop using gcc-config to control GCC version used in compat layer, since it's not needed (there is only one GCC version thanks to masking of sys-devel/gcc), and it's used incorrectly which causes problems (see #187);
• update Gentoo commit to aab8473aa90e0287553b3348a5c5b17872df4b7b (8 June 2023);
• Gentoo Prefix bootstrap script updated to commit c6db239 (2 June 2023);

closes #184, closes #185, closes #186

[eessi-bot[bot]]

Instance eessi-bot-citc-aws is configured to build:

• arch x86_64/generic for repo eessi-2021.12
• arch x86_64/generic for repo eessi-2023.04
• arch x86_64/generic for repo eessi-2023.06-compat
• arch x86_64/generic for repo eessi-2023.06-software
• arch x86_64/intel/haswell for repo eessi-2021.12
• arch x86_64/intel/haswell for repo eessi-2023.04
• arch x86_64/intel/haswell for repo eessi-2023.06-compat
• arch x86_64/intel/haswell for repo eessi-2023.06-software
• arch x86_64/intel/skylake_avx512 for repo eessi-2021.12
• arch x86_64/intel/skylake_avx512 for repo eessi-2023.04
• arch x86_64/intel/skylake_avx512 for repo eessi-2023.06-compat
• arch x86_64/intel/skylake_avx512 for repo eessi-2023.06-software
• arch x86_64/amd/zen2 for repo eessi-2021.12
• arch x86_64/amd/zen2 for repo eessi-2023.04
• arch x86_64/amd/zen2 for repo eessi-2023.06-compat
• arch x86_64/amd/zen2 for repo eessi-2023.06-software
• arch x86_64/amd/zen3 for repo eessi-2021.12
• arch x86_64/amd/zen3 for repo eessi-2023.04
• arch x86_64/amd/zen3 for repo eessi-2023.06-compat
• arch x86_64/amd/zen3 for repo eessi-2023.06-software
• arch aarch64/generic for repo eessi-2021.12
• arch aarch64/generic for repo eessi-2023.04
• arch aarch64/generic for repo eessi-2023.06-compat
• arch aarch64/generic for repo eessi-2023.06-software
• arch aarch64/graviton2 for repo eessi-2021.12
• arch aarch64/graviton2 for repo eessi-2023.04
• arch aarch64/graviton2 for repo eessi-2023.06-compat
• arch aarch64/graviton2 for repo eessi-2023.06-software
• arch aarch64/graviton3 for repo eessi-2021.12
• arch aarch64/graviton3 for repo eessi-2023.04
• arch aarch64/graviton3 for repo eessi-2023.06-compat
• arch aarch64/graviton3 for repo eessi-2023.06-software

[boegel]

bot: build arch=x86_64/generic repo=eessi-2023.06-compat bot: build arch=aarch64/generic repo=eessi-2023.06-compat

[eessi-bot[bot]]

Updates by the bot instance eessi-bot-citc-aws (click for details)

- parsing the bot command `build arch=x86_64/generic repo=eessi-2023.06-compat`, received from sender `boegel`, failed - parsing the bot command `build arch=aarch64/generic repo=eessi-2023.06-compat`, received from sender `boegel`, failed

[boegel]

The bot should be able to build this (cfr. experiment in https://github.com/boegel/compatibility-layer/pull/2), but it will complain that the build failed even though it doesn't, since the procedure to check for a correct build is still hardcoded for the software layer.

The correct tarballs will also have to created manually, because the bot/build.sh for the compat layer script tries to create the tarball outside of the build container, which doesn't work since the compat layer version that was built is not available directly via the native /cvmfs mount (which may even be missing).

This shouldn't block us from proceeding with the 2023.06 EESSI pilot version however, since we're already making good progress here (thanks to kicking out the gcc-config step, #187 is fixed, and hence the bot is able to complete the build autonomously).

[trz42]

bot: build arch=x86_64/generic repo=eessi-2023.06-compat bot: build arch=aarch64/generic repo=eessi-2023.06-compat

the following should work (= replaced with :)

bot: build arch:x86_64/generic repo:eessi-2023.06-compat
bot: build arch:aarch64/generic repo:eessi-2023.06-compat

[eessi-bot[bot]]

Updates by the bot instance eessi-bot-citc-aws (click for details)

- received bot command `build arch:x86_64/generic repo:eessi-2023.06-compat` from `trz42` - expanded format: `build architecture:x86_64/generic repository:eessi-2023.06-compat` - received bot command `build arch:aarch64/generic repo:eessi-2023.06-compat` from `trz42` - expanded format: `build architecture:aarch64/generic repository:eessi-2023.06-compat` - handling command `build architecture:x86_64/generic repository:eessi-2023.06-compat` resulted in: - submitted job `4939`, for details & status see https://github.com/EESSI/compatibility-layer/pull/188#issuecomment-1590608102 - handling command `build architecture:aarch64/generic repository:eessi-2023.06-compat` resulted in: - submitted job `4940`, for details & status see https://github.com/EESSI/compatibility-layer/pull/188#issuecomment-1590608331

[eessi-bot[bot]]

New job on instance eessi-bot-citc-aws for architecture x86_64-generic for repository eessi-2023.06-compat in job dir /mnt/shared/home/bot/eessi-bot-software-layer/jobs/2023.06/pr_188/4939	date	job status	comment
Jun 14 07:12:09 UTC 2023	submitted	job id 4939 awaits release by job manager
Jun 14 07:21:06 UTC 2023	released	job awaits launch by Slurm scheduler
Jun 14 07:53:17 UTC 2023	running	job 4939 is running
Jun 14 14:45:42 UTC 2023	finished	:cry: FAILURE Found slurm output slurm-4939.out in job dir Slurm output lacks message "No missing modules!". Slurm output lacks message about created tarball. No tarball matching eessi-\*software-\*.tar.gz found in job dir.

[eessi-bot[bot]]

New job on instance eessi-bot-citc-aws for architecture aarch64-generic for repository eessi-2023.06-compat in job dir /mnt/shared/home/bot/eessi-bot-software-layer/jobs/2023.06/pr_188/4940	date	job status	comment
Jun 14 07:12:19 UTC 2023	submitted	job id 4940 awaits release by job manager
Jun 14 07:21:04 UTC 2023	released	job awaits launch by Slurm scheduler
Jun 14 07:53:15 UTC 2023	running	job 4940 is running
Jun 14 14:45:39 UTC 2023	finished	:cry: FAILURE Found slurm output slurm-4940.out in job dir Slurm output lacks message "No missing modules!". Slurm output lacks message about created tarball. No tarball matching eessi-\*software-\*.tar.gz found in job dir.

[trz42]

Above jobs 4939 and 4940 started but the job manager crashes when trying to update the PR comments. Possibly the PAT it uses is not valid anymore :shrug:

[boegel]

Above jobs 4939 and 4940 started but the job manager crashes when trying to update the PR comments. Possibly the PAT it uses is not valid anymore 🤷

More details on the crash:

``` Traceback (most recent call last): File "/usr/lib64/python3.6/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code exec(code, run_globals) File "/mnt/shared/home/bot/eessi-bot-software-layer/eessi_bot_job_manager.py", line 723, in main() File "/mnt/shared/home/bot/eessi-bot-software-layer/eessi_bot_job_manager.py", line 704, in main job_manager.process_finished_job(known_jobs[fj]) File "/mnt/shared/home/bot/eessi-bot-software-layer/eessi_bot_job_manager.py", line 557, in process_finished_job update_comment(finished_job["comment_id"], pull_request, comment_update) File "/mnt/shared/home/bot/eessi-bot-software-layer/tools/pr_comments.py", line 95, in update_comment tries=5, delay=1, backoff=2, max_delay=30) File "/mnt/shared/home/bot/.local/lib/python3.6/site-packages/retry/api.py", line 101, in retry_call return __retry_internal(partial(f, *args, **kwargs), exceptions, tries, delay, max_delay, backoff, jitter, logger) File "/mnt/shared/home/bot/.local/lib/python3.6/site-packages/retry/api.py", line 33, in __retry_internal return f() File "/mnt/shared/home/bot/.local/lib/python3.6/site-packages/github/IssueComment.py", line 131, in edit "PATCH", self.url, input=post_parameters File "/mnt/shared/home/bot/.local/lib/python3.6/site-packages/github/Requester.py", line 355, in requestJsonAndCheck verb, url, parameters, headers, input, self.__customConnection(url) File "/mnt/shared/home/bot/.local/lib/python3.6/site-packages/github/Requester.py", line 378, in __check raise self.__createException(status, responseHeaders, output) github.GithubException.GithubException: 403 {"message": "Resource not accessible by integration", "documentation_url": "https://docs.github.com/rest/reference/issues#update-an-issue-comment"} ```

[boegel]

bot: foobar

[eessi-bot[bot]]

Updates by the bot instance eessi-bot-citc-aws (click for details)

- received bot command `foobar` from `boegel` - expanded format: `foobar` - handling command `foobar` failed with message _unknown command `foobar`; use `bot: help` for usage information_