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

Add action to test newer hdf5 version #925

Merged
merged 6 commits into from
Dec 9, 2023
Merged

Conversation

bquan0
Copy link
Contributor

@bquan0 bquan0 commented Dec 5, 2023

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 of hdf5_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 the linux_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.

@bquan0 bquan0 requested a review from gonuke December 5, 2023 16:05
@gonuke
Copy link
Member

gonuke commented Dec 6, 2023

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
Copy link
Member

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?

@bquan0
Copy link
Contributor Author

bquan0 commented Dec 8, 2023

Looks like the workflow for hdf5_version: 1.14.0 worked. I've just edited it to be 1.14.3, so we'll see if that works too.
I also mapped the hdf5 workflow badge to my repo and branch just to see if it would work. That's something I'll have to change before this PR gets merged.

@gonuke
Copy link
Member

gonuke commented Dec 8, 2023

Thanks @bquan0 - I think this looks OK - go ahead and switch back the README and I'll merge.

Copy link
Member

@gonuke gonuke left a comment

Choose a reason for hiding this comment

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

Thanks @bquan0

@gonuke gonuke merged commit a5e7e0f into svalinn:develop Dec 9, 2023
8 checks passed
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