-
Notifications
You must be signed in to change notification settings - Fork 65
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
Add action to test newer hdf5 version #925
Conversation
Are you able to manually launch this action on your fork? Also, please look at the bottom of the README to add a badge for this, as well. |
uses: ./.github/actions/upstream-test | ||
with: | ||
token: ${{ secrets.GITHUB_TOKEN }} | ||
hdf5_version: 1.14.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we go straight to 1.14.3 instead?
Looks like the workflow for |
Thanks @bquan0 - I think this looks OK - go ahead and switch back the README and I'll merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @bquan0
Description
I made a copy of one of the
linux_upstream_test.yml
files and modified it slightly to use the composite action with an argument ofhdf5_version: 1.14
as specified in #916. I'm guessing this is what the issue is asking me to do? I'm not entirely sure because it wasn't specific. The issue also mentions that there are interactions between dependencies, which can be easily added with a matrix in thelinux_upstream_test_hdf5.yml
file. However, I don't know what interactions need to be tested, so I didn't add the matrix just yet.Behavior
New behavior is that there will be one more action run when PRs are merged to
develop
that will test whether DAGMC works with version 1.14 of hdf5.