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.

Sign up for GitHub

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

Jump to bottom

Reenable CUDA + valgrind CI configuration #1367

Open
msimberg opened this issue Dec 9, 2024 · 0 comments
Open

Reenable CUDA + valgrind CI configuration #1367

msimberg opened this issue Dec 9, 2024 · 0 comments
Labels
category: CI Continuous Integration category: CUDA effort: 3 A few days of work. priority: medium This should be done sooner or later. type: feature

Comments

@msimberg
Copy link
Contributor

msimberg commented Dec 9, 2024

#1239 disables valgrind testing on the CUDA CI configuration, since valgrind on aarch64 is either noisy for no good reason, or pika is buggy there. We have to investigate which case it is and try to enable valgrind testing with CUDA again. After Piz Daint goes down we have no x86/CUDA systems to test on anymore (at least in the short term). We only test with valgrind on GitHub actions without CUDA.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
category: CI Continuous Integration category: CUDA effort: 3 A few days of work. priority: medium This should be done sooner or later. type: feature
Projects
pika planning board
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@msimberg