-
Notifications
You must be signed in to change notification settings - Fork 2.2k
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
ascent@0.9.1 (and @0.9.2) +cuda fails on ARM, POWER, and AMD64: runtimes/expressions/ascent_execution_policies.hpp(135): error: namespace "RAJA" has no member "cuda_exec" #38045
Comments
@eugeneswalker it seems like an config issue or header confusing related to raja cuda vs non cuda. Not sure how it would get crossed. Is there a way I can try to reproduce? |
Yes, here are the two Spack environments you can use: And here are Docker images you can use to replicate the environment exactly: The ascent dependencies are available in our build cache. You should be able to install them quickly without building them from source:
Here are full reproducer steps for POWER:
To reproduce on ARM is the same as above, but you would use the ARM Docker image + ARM Spack environment. Can you reproduce using these instructions? |
Thanks for the details, I'll get this in my queue to investigate. |
Any update on this? I'm seeing this the same problem
|
Sorry no updates, several spack things seemed to have atrophied as spack has moved forward. We have had to rely on other scripts for primary development and deployment and to meet ECP milestones. We would still like our spack to be healthy outside of our forks, but don't have resources right now. Maybe we can try again in a future ascent release that will use newer RAJA + CAMP |
Steps to reproduce the issue
asccent@0.9.1 +cuda
build fails on ARM and PPC64LE using:spack@develop
(9ee2d79 fromTue May 16 13:32:26 2023 -0500
)Concretization
Error:
Error message
Error message
Information on your system
Additional information
spack-build-env.txt
spack-build-out.txt
@cyrush @kwryankrattiger @wspear @nchaimov
General information
spack debug report
and reported the version of Spack/Python/Platformspack maintainers <name-of-the-package>
and @mentioned any maintainersThe text was updated successfully, but these errors were encountered: