Skip to content
This repository was archived by the owner on Jan 28, 2022. It is now read-only.

Conversation

tristan0x
Copy link
Member

@tristan0x tristan0x commented Oct 22, 2018

This pull-request adds capability to specify Spack specs in YAML that are installed before executing benchmarks.

@coveralls
Copy link

coveralls commented Oct 22, 2018

Coverage Status

Coverage increased (+0.1%) to 84.541% when pulling 16d1330 on enh/spack into 51948fb on master.

@tristan0x tristan0x force-pushed the enh/spack branch 5 times, most recently from e245572 to 7307719 Compare October 23, 2018 11:31
Copy link
Contributor

@ohm314 ohm314 left a comment

Choose a reason for hiding this comment

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

Overall very cool - just one question I had on the yaml format for spack.

test01:
type: stream
spack:
specs:
Copy link
Contributor

Choose a reason for hiding this comment

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

As mentioned also in the other repo. do we really need this additional level. It seems redundant, or do you think in the future we might have other spack functions that would go in there?

Copy link
Member Author

Choose a reason for hiding this comment

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

Thank you for the feedback. I agree this extra level is a pain, but as I am not expert at spack, I prefered to leave space for future changes.

Copy link
Contributor

@ohm314 ohm314 left a comment

Choose a reason for hiding this comment

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

my question in my previous review can also be addressed later.

@tristan0x tristan0x merged commit f4c28e9 into master Nov 5, 2018
@tristan0x tristan0x deleted the enh/spack branch November 5, 2018 07:19
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants