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

Don't run n=10000 problem size of pidigits5 in valgrind #19257

Merged
merged 1 commit into from
Feb 16, 2022

Conversation

bradcray
Copy link
Member

In the "Brad can be a slow learner" category, this moves the .execopts
that I applied to my study version of pidigits (in #19189 to avoid a
valgrind timeout) over to the snapshot of the submitted version.
Since my version is now simple / serial, I also restored the
traditional .execopts for my study version.

In the "Brad can be a slow learner" category, this moves the .execopts
that I applied to my study version of pidigits (in chapel-lang#19189 to avoid a
valgrind timeout) over to the snapshot of the submitted version.
Since my version is now simple / serial, I also restored the
traditional .execopts for my study version.

---
Signed-off-by: Brad Chamberlain <bradcray@users.noreply.github.com>
@bradcray bradcray merged commit 553f7cf into chapel-lang:main Feb 16, 2022
@bradcray bradcray deleted the fix-pidigits-valgrind-timeout branch February 16, 2022 22:12
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.

1 participant