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

Allow for empty spack env #349

Merged
merged 7 commits into from
Jan 19, 2024

Conversation

rfbgo
Copy link
Collaborator

@rfbgo rfbgo commented Dec 13, 2023

Follow on from #336 which I think did not do what was intended

I want to be able to support something like:

 42     environments:
 43       app_name: {}

This gives a len(self.env_contents) == 0 so is currently considered invalid.

This PR instead lets it continue and hash an empty dict

@rfbgo rfbgo marked this pull request as draft December 13, 2023 16:57
lib/ramble/ramble/spack_runner.py Outdated Show resolved Hide resolved
lib/ramble/ramble/spack_runner.py Outdated Show resolved Hide resolved
lib/ramble/ramble/experimental/uploader.py Outdated Show resolved Hide resolved
lib/ramble/ramble/spack_runner.py Show resolved Hide resolved
@rfbgo rfbgo force-pushed the empty_env branch 2 times, most recently from afc0df1 to 7f48227 Compare January 16, 2024 23:01
This is a little controversial, as it is not super obvious what a
dry-run means in the context of analyze, but is required in order for us
to both:

1) Analzye non-setup workspaces (such as those that have results but you
   no longer have the soft env); and
2) Reasonably unit-test software without significant setup

The semantic is close to "reduced errors" where by you can continue if a
workspace is not setup, and perhaps missing files that setup would
normally be required to produce
@rfbgo rfbgo marked this pull request as ready for review January 17, 2024 00:01
@douglasjacobsen douglasjacobsen merged commit 424fd0f into GoogleCloudPlatform:develop Jan 19, 2024
5 checks passed
linsword13 added a commit to linsword13/ramble that referenced this pull request Aug 2, 2024
Currently under `workspace` cmd, there are three subcommands that
support `--dry-run`:

* `setup`: WAI
* `mirror`: the dry-run is used by the `software_create_env` and the
  `mirror_software` stages (spack support only). Updated the help text
  to make it clearer
* `analyze`: the dry-run is used to proceed on partially setup workspace
  (GoogleCloudPlatform#349.) The
  usefulness on having this for analyze is debatable, but keeping it for
  now. Only update the help text for better clarity.
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.

2 participants