Interim model-db Update: Only Ingest Gadi Metadata
#214
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CodeGat
added
type:enhancement
CodeGat
force-pushed
the
212-interim-model-db-fix
branch
from
2f76d7f to
a0f0bbe
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #212
Background
Currently, the
model-dbsection of the multi-target workflow doesn't work, because we renamed a bunch of the metadata/outputs to have target-specific filenames (e.gGadi.spack.lock,deploy-outputs.Gadi).In this PR, we are restoring the original functionality in which the
model-dbis updated withGadi-specific information, until we have an updated provenance database, which will come about through ACCESS-NRI/tracking-services#23.In this PR:
Testing
Tested using the updated
tests/scripts/generate-build-metadatatests.