Skip to content
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

spack-stack-1.8.0 release tasks #1278

Closed
74 tasks done
climbfuji opened this issue Aug 29, 2024 · 26 comments · Fixed by #1332
Closed
74 tasks done

spack-stack-1.8.0 release tasks #1278

climbfuji opened this issue Aug 29, 2024 · 26 comments · Fixed by #1332

Comments

@climbfuji
Copy link
Collaborator

climbfuji commented Aug 29, 2024

Tasks for the spack-stack-1.8.0 release:

@RatkoVasic-NOAA
Copy link
Collaborator

RatkoVasic-NOAA commented Aug 29, 2024

Started working on Hera. It concretized OK.
Installation in under way. There is one problem with crtm_fix:

==> Installing crtm-fix-2.4.0.1_emc-al2juhzkilqssvyg75jsni664uhcknls [21/291]
==> No binary for crtm-fix-2.4.0.1_emc-al2juhzkilqssvyg75jsni664uhcknls found: installing from source
==> Error: FetchError: All fetchers failed for spack-stage-crtm-fix-2.4.0.1_emc-al2juhzkilqssvyg75jsni664uhcknls
==> Warning: Skipping build of crtm-2.4.0.1-fvusealmjzqzvr2tjoe7b4gfxkhfil4x since crtm-fix-2.4.0.1_emc-al2juhzkilqssvyg75jsni664uhcknls failed

I saw this on Jet as well. It looks like we cannot access crtm-fix-2.4.0.1_emc.

and another:

==> Installing libpthread-stubs-0.5-75nwhcat2k4nkuzlmnzow5iisqi5x4ct [35/291]
==> No binary for libpthread-stubs-0.5-75nwhcat2k4nkuzlmnzow5iisqi5x4ct found: installing from source
==> Error: FetchError: All fetchers failed for spack-stage-libpthread-stubs-0.5-75nwhcat2k4nkuzlmnzow5iisqi5x4ct
==> Warning: Skipping build of libxcb-1.16-bdkenjctf4jxkkzk73cnoiztl6cqjztm since libpthread-stubs-0.5-75nwhcat2k4nkuzlmnzow5iisqi5x4ct failed

@climbfuji
Copy link
Collaborator Author

Can you try to rerun the install for crtm-fix with spack -d install ... - that might give you more information. If you can't access those files from hera (which shouldn't be the case), then you can try to create a mirror on another machine and update the spack source-cache on hera.

@RatkoVasic-NOAA
Copy link
Collaborator

Can you try to rerun the install for crtm-fix with spack -d install ... - that might give you more information. If you can't access those files from hera (which shouldn't be the case), then you can try to create a mirror on another machine and update the spack source-cache on hera.

Didn't try for crtm-fix, but there are others that failed with "All fetchers failed", but when I tried to download them manually on Hera, download was OK.

@srherbener
Copy link
Collaborator

@climbfuji I'm going to start the build on Discover SCU16. Where do I place the release candidate, and what do I name it? Perhaps: /gpfsm/dswdev/jcsda/spack-stack/scu16/spack-stack-rc-1.8.0

@climbfuji
Copy link
Collaborator Author

I use spack-stack-1.8.0-rc1 but it's up to you of course. If the path is longer than the final spack-stack-1.8.0 install, then you can use the release candidate to create a binary cache and install from it when you do the final 1.8.0 install.

@srherbener
Copy link
Collaborator

Thanks @climbfuji. I just wanted to make sure I'm following a best practice. Not sure I understand your comment about the binary cache. I created /gpfsm/dswdev/jcsda/spack-stack/scu16/spack-stack-rc-1.8.0 and will that satisfy the requirement to be able to use the binary cache for the final install?

@climbfuji
Copy link
Collaborator Author

If you use the same names for the environments, then yes. spack-stack-1.8.0 has three characters less than spack-stack-rc-1.8.0.

@RatkoVasic-NOAA
Copy link
Collaborator

RatkoVasic-NOAA commented Aug 30, 2024

Hera:
installed ue-intel (had to use mirror from Hercules): /contrib/spack-stack/spack-stack-1.8.0/envs/ue-intel
ue-gcc installation in progress: /contrib/spack-stack/spack-stack-1.8.0/envs/ue-gcc
For now, only change goes to site/mirrors.yaml

@climbfuji
Copy link
Collaborator Author

@RatkoVasic-NOAA I am confused a bit - because of the recent changes to how we build ecflow, I was expecting site config and documentation updates for Hera - removal of external ecflow, addition of external qt5 if not already there, etc. See #1257

@srherbener
Copy link
Collaborator

srherbener commented Aug 30, 2024

I am building the release candidates on Discover SCU16, and @ashley314 will test these.

  • GCC: /gpfsm/dswdev/jcsda/spack-stack/scu16/spack-stack-rc-1.8.0/envs/ue-gcc-12.1.0
  • Intel: /gpfsm/dswdev/jcsda/spack-stack/scu16/spack-stack-rc-1.8.0/envs/ue-intel-2021.6.0

Checked box means the environment is ready to test.

@climbfuji
Copy link
Collaborator Author

climbfuji commented Aug 30, 2024

I am building the release candidates on Discover SCU16, and @ashley314 will test these.

  • GCC: /gpfsm/dswdev/jcsda/spack-stack/scu16/spack-stack-rc-1.8.0/envs/ue-gcc-12.1.0
  • Intel: /gpfsm/dswdev/jcsda/spack-stack/scu16/spack-stack-rc-1.8.0/envs/ue-intel-2021.6.0

Checked box means the environment is ready to test.

Just want to double-check that you made the ecflow/qt5 changes (see #1257)?

@srherbener
Copy link
Collaborator

Sorry I didn't add ecflow to the config - too many things going on at once. I'll go do that now.

@climbfuji
Copy link
Collaborator Author

climbfuji commented Aug 30, 2024

We don't want ecflow in the site configs. We want only qt@5 so that spack-stack builds ecflow. (Basically what we did on S4)

@climbfuji
Copy link
Collaborator Author

Therefore, we can likely remove the external miniconda and ecflow dependencies for spack-stack, too.

@climbfuji
Copy link
Collaborator Author

Therefore, we can likely remove the external miniconda and ecflow dependencies for spack-stack, too.

Whether you then need a module use /some/path/to/jedis/modules at all or not depends on where the qt and mysql are coming from.

@srherbener
Copy link
Collaborator

@ashley314 Discover SCU16 gcc environment is now ready for testing. It includes ecflow in the stack (and qt@5 is an external package).

@srherbener
Copy link
Collaborator

@ashley314 Discover SCU16 gcc environment is now ready for testing. It includes ecflow in the stack (and qt@5 is an external package).

Discover SCU16 Intel environment is now ready for testing.

@DavidHuber-NOAA
Copy link
Collaborator

DavidHuber-NOAA commented Sep 16, 2024

Could the gsi-addon environment also be installed on these platforms: Hera, Jet, Orion, Hercules, Gaea C5 (C6 optional), all three PW CSPs, and S4. EDIT: This environment is only required for the Intel compiler suite.

@RatkoVasic-NOAA
Copy link
Collaborator

@DavidHuber-NOAA Yes, as soon as we install 1.8.0 on those machines. Some of them are ready for addons (Hera and Jet).

@RatkoVasic-NOAA
Copy link
Collaborator

@DavidHuber-NOAA I added GSI addon to Hera spack-stack-1.8.0:
/contrib/spack-stack/spack-stack-1.8.0/envs/gsi-intel-2021.5.0/install/modulefiles/Core
Notice some name changes.
Also, here are changes for GSI modulefiles:

gsi_hera.intel.lua:
prepend_path("MODULEPATH", "/contrib/spack-stack/spack-stack-1.8.0/envs/gsi-intel-2021.5.0/install/modulefiles/Core")
local python_ver=os.getenv("python_ver") or "3.11.7"
local stack_impi_ver=os.getenv("stack-intel-oneapi-mpi") or "2021.5.1"
local cmake_ver=os.getenv("cmake_ver") or "3.28.1"

gsi_common.lua:
local bufr_ver=os.getenv("bufr_ver") or "12.1.0"
local ip_ver=os.getenv("ip_ver") or "5.0.0"

@climbfuji
Copy link
Collaborator Author

Please make sure all site config and documentation updates are in the spack-stack release branch (incl the readthedocs documentation if applicable) and in https://github.com/JCSDA/spack-stack/wiki/spack%E2%80%90stack%E2%80%901.8.0-release-documentation - THANK YOU!

@RatkoVasic-NOAA
Copy link
Collaborator

@DavidHuber-NOAA Just finished GSI addon on Jet:
/contrib/spack-stack/spack-stack-1.8.0/envs/gsi-intel-2021.5.0/install/modulefiles/Core
Exactly same changes to Jet modulefiles like for Hera.

@DavidHuber-NOAA
Copy link
Collaborator

Great, thank you @RatkoVasic-NOAA!

@ashley314
Copy link
Collaborator

FYI, I found a typo for discover-scu17 in configs/sites/tier1/discover-scu17/packages_intel.yaml.

@climbfuji
Copy link
Collaborator Author

FYI, I found a typo for discover-scu17 in configs/sites/tier1/discover-scu17/packages_intel.yaml.

Please create a PR for release/1.8.0 with all changes needed for the discover platforms. Thanks!

@RatkoVasic-NOAA
Copy link
Collaborator

RatkoVasic-NOAA commented Sep 25, 2024

@DavidHuber-NOAA Current list of gsi addons to 1.8.0:

Hera: /contrib/spack-stack/spack-stack-1.8.0/envs/gsi-intel-2021.5.0/install/modulefiles/Core
Jet: /contrib/spack-stack/spack-stack-1.8.0/envs/gsi-intel-2021.5.0/install/modulefiles/Core
Gaea-C5: /ncrc/proj/epic/spack-stack/c6/spack-stack-1.8.0/envs/gsi-intel-2021.10.0/install/modulefiles/Core
Gaea-C6: /ncrc/proj/epic/spack-stack/spack-stack-1.8.0/envs/gsi-intel-2021.9.0/install/modulefiles/Core
NOAA-AWS: /contrib/spack-stack-rocky8/spack-stack-1.8.0/envs/gsi-intel-2021.10.0/install/modulefiles/Core

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

8 participants