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

Accommodate separate lmod, tcl modules.yaml's #329

Merged

Conversation

AlexanderRichert-NOAA
Copy link
Collaborator

Description

This PR updates the 'create env' command in order to support the separation of common/modules.yaml into lmod and tcl ones.

Issue(s) addressed

Addresses JCSDA/spack-stack#703, JCSDA/spack-stack#50

Dependencies

none

Checklist

  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation
  • I have run the unit tests before creating the PR

Copy link
Collaborator

@srherbener srherbener left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These changes look okay to me, but I haven't tested. I'm relying on the CI testing.

Copy link
Collaborator

@climbfuji climbfuji left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great, thanks. Any possibilities to include it in the unit tests here and also in the spack-stack unit tests?

lib/jcsda-emc/spack-stack/stack/stack_env.py Outdated Show resolved Hide resolved
@AlexanderRichert-NOAA
Copy link
Collaborator Author

AlexanderRichert-NOAA commented Sep 30, 2023

@climbfuji I don't see the jcsda-emc unit tests getting run anywhere, am I missing something? I added a line to unit_tests.yaml just now that I think will run them. EDIT: nevermind, got it :)

@climbfuji
Copy link
Collaborator

This looks great, I am testing this now on my macOS.

Copy link
Collaborator

@climbfuji climbfuji left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a problem with spack parsing the double colons in the site modules.yaml file, see attached screenshot (from my macOS where the default is lmod, i.e. an unchanged environment (no --modulesys option) is fine, but the modified env is not.

Screen Shot 2023-10-09 at 8 41 28 AM

@AlexanderRichert-NOAA
Copy link
Collaborator Author

I saw the same thing in my testing, but it didn't seem to negatively impact anything. Is it breaking the test environment/keeping you from installing?

@climbfuji
Copy link
Collaborator

I saw the same thing in my testing, but it didn't seem to negatively impact anything. Is it breaking the test environment/keeping you from installing?

I haven't tried that, but I know we added some logic for the containers previously (I might have been able to remove that in the last container PR, don't remember) that replaced the double colons. I can give that a try, but it would be cleaner if we didn't have these malformatted yaml files.

@AlexanderRichert-NOAA
Copy link
Collaborator Author

Okay. I'd prefer to leave as-is if we can, but if needed we can always run a search and replace on the output file to get rid of the apostrophes.

@climbfuji
Copy link
Collaborator

climbfuji commented Oct 10, 2023 via email

Copy link
Collaborator

@climbfuji climbfuji left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perfect, thanks very much for this. Works like a charm on my macOS laptop.

@climbfuji climbfuji merged commit 0669aca into JCSDA:jcsda_emc_spack_stack Oct 11, 2023
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.

3 participants