You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Charles E. Rolke (Jira)" <ji...@apache.org> on 2020/08/05 18:20:00 UTC
[jira] [Commented] (PROTON-2230) Valgrind and Sanitizer issues in
c-threaderciser test
[ https://issues.apache.org/jira/browse/PROTON-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17171666#comment-17171666 ]
Charles E. Rolke commented on PROTON-2230:
------------------------------------------
What is the status of the c-threaderciser test? Are failures expected?
This test is failing with timeout on Fedora 31.
* Timeout failure gives no clue as to what went wrong
* threaderciser test appears to ignore the ctest --timeout command line option so giving the test more time is not possible
Here is a passing run (the one and only pass in about 15 tries):
{code:java}
> ctest -VV -R c-threaderciser --time=10000000000
UpdateCTestConfiguration from :/home/chug/git/qpid-proton/build/DartConfiguration.tcl
Parse Config file:/home/chug/git/qpid-proton/build/DartConfiguration.tcl
UpdateCTestConfiguration from :/home/chug/git/qpid-proton/build/DartConfiguration.tcl
Parse Config file:/home/chug/git/qpid-proton/build/DartConfiguration.tcl
Test project /home/chug/git/qpid-proton/build
Constructing a list of tests
Done constructing a list of tests
Updating test list for fixtures
Added 0 tests to meet fixture requirements
Checking test dependency graph...
Checking test dependency graph end
test 6
Start 6: c-threaderciser
6: Test command: /usr/bin/python "/home/chug/git/qpid-proton/scripts/env.py" "--" "TEST_EXE_PREFIX=/usr/bin/valgrind --tool=memcheck --leak-check=full --error-exitcode=42 --quiet --suppressions=/home/chug/git/qpid-proton/tests/valgrind.supp" "/usr/bin/valgrind" "--tool=memcheck" "--leak-check=full" "--error-exitcode=42" "--quiet" "--suppressions=/home/chug/git/qpid-proton/tests/valgrind.supp" "/home/chug/git/qpid-proton/build/c/tests/c-threaderciser"
6: Test timeout computed to be: 120
6: threaderciser start: threads=8, time=1, actions=[listen, close-listen, connect, close-connect, wake, timeout, cancel-timeout]
1/1 Test #6: c-threaderciser .................. Passed 74.56 sec
The following tests passed:
c-threaderciser
100% tests passed, 0 tests failed out of 1
{code}
Test timeouts appear to be handled incorrectly:
{code:java}
# Run ctest with timeout=300 years
ctest -VV -R c-threaderciser --time=10000000000
# Test cli reports time=1
6: threaderciser start: threads=8, time=1, actions=[listen, close-listen, connect, close-connect, wake, timeout, cancel-timeout]
# Ctest reports test passing in 74.56 sec
1/1 Test #6: c-threaderciser .................. Passed 74.56 sec
{code}
After threaderciser start the timout cases simply report
{code:java}
1/1 Test #6: c-threaderciser ..................***Timeout 120.11 sec
{code}
Since this is not a Valgrind or Sanitizer issue maybe it should be reported as a separate issue. Yes? And this is git master@550dd
> Valgrind and Sanitizer issues in c-threaderciser test
> -----------------------------------------------------
>
> Key: PROTON-2230
> URL: https://issues.apache.org/jira/browse/PROTON-2230
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Affects Versions: proton-c-0.31.0
> Reporter: Jiri Daněk
> Priority: Major
>
> As described in PROTON-2225, the test is not passing cleanly under Valgrind and Sanitizers. Currently, the issues are suppressed and the entries in suppression file are marked with TODO comments.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org