Skip to content

e4s: add hypre +rocm#32148

Merged
tldahlgren merged 1 commit intospack:developfrom
eugeneswalker:e4s-add-hypre-rocm
Oct 10, 2022
Merged

e4s: add hypre +rocm#32148
tldahlgren merged 1 commit intospack:developfrom
eugeneswalker:e4s-add-hypre-rocm

Conversation

@eugeneswalker
Copy link
Copy Markdown
Contributor

add hypre +rocm to E4S stack

FYI @wspear @balay @osborn9 @ulrikeyang

@eugeneswalker eugeneswalker added e4s ROCm/hip Support for ROCm/hip labels Aug 15, 2022
@spackbot-app spackbot-app bot added core PR affects Spack core functionality gitlab Issues related to gitlab integration labels Aug 15, 2022
@eugeneswalker eugeneswalker reopened this Aug 15, 2022
tldahlgren
tldahlgren previously approved these changes Aug 15, 2022
Copy link
Copy Markdown
Contributor

@tldahlgren tldahlgren left a comment

Choose a reason for hiding this comment

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

LGTM. Hopefully it builds successfully.

@tldahlgren tldahlgren self-assigned this Aug 15, 2022
@tldahlgren tldahlgren enabled auto-merge (squash) August 15, 2022 21:35
@adamjstewart
Copy link
Copy Markdown
Member

Probably worth merging all E4S CI PRs into a single PR. Btw, doc tests are broken on develop, so you'll need to rebase all PRs after those are fixed.

@tldahlgren
Copy link
Copy Markdown
Contributor

Probably worth merging all E4S CI PRs into a single PR. Btw, doc tests are broken on develop, so you'll need to rebase all PRs after those are fixed.

FWIW. If there's a chance that any of these fail I think there's value in having them in separate PRs in the sense that it is a way to allow maintainers to know that it is their package that has issues in the stack, at least when it is first added.

@adamjstewart
Copy link
Copy Markdown
Member

Def makes it simpler to debug, although it's going to be fun to resolve merge constraints in all PRs since they all touch the same file. Also creates a lot of redundant CI runs...

@eugeneswalker
Copy link
Copy Markdown
Contributor Author

Probably worth merging all E4S CI PRs into a single PR. Btw, doc tests are broken on develop, so you'll need to rebase all PRs after those are fixed.

FWIW. If there's a chance that any of these fail I think there's value in having them in separate PRs in the sense that it is a way to allow maintainers to know that it is their package that has issues in the stack, at least when it is first added.

This was my thought. I'd rather have them all in one, but having them individually will leave a record of the failures that we can reference with maintainers and other stakeholders while allowing us to merge others.

@eugeneswalker
Copy link
Copy Markdown
Contributor Author

Also creates a lot of redundant CI runs...

Are you talking about the GitLab pipeline builds? Why would it create redundant runs? It should only build the affected package, in this case the package being uncommented.

tldahlgren
tldahlgren previously approved these changes Aug 16, 2022
@tldahlgren
Copy link
Copy Markdown
Contributor

@eugeneswalker
Copy link
Copy Markdown
Contributor Author

Looks like the package fails to build. See https://gitlab.spack.io/spack/spack/-/jobs/3028886.

...
     191    In file included from device_utils.c:10:
  >> 192    ./_hypre_utilities.hpp:116:10: fatal error: 'rocsparse.h' file not 
            found
     193    #include <rocsparse.h>
     194             ^~~~~~~~~~~~~
     195    1 error generated when compiling for gfx90a.
...

@eugeneswalker
Copy link
Copy Markdown
Contributor Author

@eugeneswalker
Copy link
Copy Markdown
Contributor Author

Rebased on develop following resolution of #32194 (comment) via merge of PR #33073 (comment)

@eugeneswalker eugeneswalker requested a review from wspear October 10, 2022 15:59
@eugeneswalker
Copy link
Copy Markdown
Contributor Author

@spackbot run pipeline

@spackbot-app
Copy link
Copy Markdown

spackbot-app bot commented Oct 10, 2022

I've started that pipeline for you!

@tldahlgren tldahlgren merged commit dc141f5 into spack:develop Oct 10, 2022
luke-dt pushed a commit to dantaslab/spack that referenced this pull request Oct 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core PR affects Spack core functionality e4s gitlab Issues related to gitlab integration ROCm/hip Support for ROCm/hip

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants