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
runtests: increase valgrind max thread count limit #9140
Conversation
By default, valgrind limits the number of threads in the target program to 500 while test 3026 creates at least 1000. Increase the valgrind limit to avoid a systematic test 3026 failure.
This can be an alternate solution if this satisfies the test requirements. |
Hi Jay, Is this a fix for the below ?
|
I don't know, run that specific test and check the output: |
I think expanding it to the other platforms is the right thing to do. The mentioned failure happened in Linux. |
I too think it would rather be better to reduce the number of threads in the test. |
I will improve my PR regarding this tonight. |
A bit more details into the error
Looks like this commit introduced the error, is there a way to skip this test while doing |
@SukanyaHanumanthu: No, this PR does not fix your error.
You can locally add 3026 in |
This PR is no longer needed: test 3026 thread count has been reduced to 100 by commit 0484127. |
By default, valgrind limits the number of threads in the target program
to 500 while test 3026 creates at least 1000.
Increase the valgrind limit to avoid a systematic test 3026 failure.