-
Notifications
You must be signed in to change notification settings - Fork 50
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
Rebuild hatchling-1.18.0-GCCcore-12.3.0 #669
Rebuild hatchling-1.18.0-GCCcore-12.3.0 #669
Conversation
Instance
|
Instance
|
Instance
|
bot: build repo:eessi.io-2023.06-software arch:aarch64/neoverse_n1 |
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
Updates by the bot instance
|
Looking at the build log we see:
This is almost certainly the same @bedroge reports in #556 and worked around here: #555 (comment) |
bot: build repo:eessi.io-2023.06-software arch:aarch64/neoverse_n1 |
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
Failed test:
|
bot: build repo:eessi.io-2023.06-software arch:aarch64/neoverse_n1 |
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
bot: build repo:eessi.io-2023.06-software arch:x86_64/intel/skylake_avx512 |
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
My mistake, did not add write permissions recursively. bot: build repo:eessi.io-2023.06-software arch:x86_64/intel/skylake_avx512 |
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
Hmm, I only see this in build log:
Aren't we missing a |
Interesting, I figured just adding the easyconfig to the rebuild easystack would trigger it as a rebuild in zen4 as well 🤔 Maybe I'm missing a step... |
I dont think it should be different for zen4. Dont have time to check logs now, but we should check if it goes into the Line 188 in 1fc0cb7
This should remove the installation in the overlay. Since the same overlay is then used at Build time (or should be, at least), we don't actually need |
Checked the logs, the removal step fails, since some
|
Workaround has been put in place to fix |
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen4 |
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
bot: build repo:eessi.io-2023.06-software arch:aarch64/a64fx |
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
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.
lgtm
Hmm, also seeing this when rebuilding
Same problem as we saw with
Problem is this time there's no easy fix, since we don't have control over the configuration of the workernode on which we're running... So it seems like we need to re-visit the use of Thoughts here @casparvl? |
@Neves-P has manually removed bot: build repo:eessi.io-2023.06-software arch:aarch64/a64fx |
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
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.
lgtm
Manually removed old tarballs and added new ones. Procedure: #!/bin/bash
# Remove and replace hatchling 1.18.0 GCCcore-12.3.0 PR 669 - Pedro Santos Neves
# Remove existing installs (A64FX was removed previously in order to build)
rm -rf /cvmfs/software.eessi.io/versions/2023.06/software/linux/x86_64/amd/zen2/software/hatchling/1.18.0-GCCcore-12.3.0
rm -rf /cvmfs/software.eessi.io/versions/2023.06/software/linux/x86_64/amd/zen3/software/hatchling/1.18.0-GCCcore-12.3.0
rm -rf /cvmfs/software.eessi.io/versions/2023.06/software/linux/x86_64/amd/zen4/software/hatchling/1.18.0-GCCcore-12.3.0
rm -rf /cvmfs/software.eessi.io/versions/2023.06/software/linux/x86_64/intel/haswell/software/hatchling/1.18.0-GCCcore-12.3.0
rm -rf /cvmfs/software.eessi.io/versions/2023.06/software/linux/x86_64/intel/skylake_avx512/software/hatchling/1.18.0-GCCcore-12.3.0
rm -rf /cvmfs/software.eessi.io/versions/2023.06/software/linux/x86_64/generic/software/hatchling/1.18.0-GCCcore-12.3.0
rm -rf /cvmfs/software.eessi.io/versions/2023.06/software/linux/aarch64/generic/software/hatchling/1.18.0-GCCcore-12.3.0
rm -rf /cvmfs/software.eessi.io/versions/2023.06/software/linux/aarch64/neoverse_n1/software/hatchling/1.18.0-GCCcore-12.3.0
rm -rf /cvmfs/software.eessi.io/versions/2023.06/software/linux/aarch64/neoverse_v1/software/hatchling/1.18.0-GCCcore-12.3.0
# Move to software dir
cd /cvmfs/software.eessi.io/versions
# Unpack tarballs
tar xvzf /srv/tmp/tarballs/eessi-2023.06-software-linux-aarch64-a64fx-1724259587.tar.gz
tar xvzf /srv/tmp/tarballs/eessi-2023.06-software-linux-x86_64-amd-zen4-1724152985.tar.gz
tar xvzf /srv/tmp/tarballs/eessi-2023.06-software-linux-x86_64-intel-haswell-1723819673.tar.gz
tar xvzf /srv/tmp/tarballs/eessi-2023.06-software-linux-x86_64-amd-zen3-1723819613.tar.gz
tar xvzf /srv/tmp/tarballs/eessi-2023.06-software-linux-x86_64-amd-zen2-1723819605.tar.gz
tar xvzf /srv/tmp/tarballs/eessi-2023.06-software-linux-x86_64-generic-1723819622.tar.gz
tar xvzf /srv/tmp/tarballs/eessi-2023.06-software-linux-aarch64-neoverse_v1-1723819484.tar.gz
tar xvzf /srv/tmp/tarballs/eessi-2023.06-software-linux-aarch64-generic-1723819504.tar.gz
tar xvzf /srv/tmp/tarballs/eessi-2023.06-software-linux-x86_64-intel-skylake_avx512-1723817335.tar.gz
tar xvzf /srv/tmp/tarballs/eessi-2023.06-software-linux-aarch64-neoverse_n1-1723805793.tar.gz Looks as expected AFAICS. If everything looks good, PR can be closed (or merged?) |
Verified, looks good:
|
Following from: https://gitlab.com/eessi/support/-/issues/85