stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Travis Vitek (JIRA)" <j...@apache.org>
Subject [jira] Commented: (STDCXX-536) allow thread safety tests to time out without failing
Date Tue, 11 Sep 2007 00:34:30 GMT

    [ https://issues.apache.org/jira/browse/STDCXX-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526315
] 

Travis Vitek commented on STDCXX-536:
-------------------------------------


I'm not convinced that this is actually a smart thing to do. Tests that would noramlly time
out will now exit successfully. This is probably okay if there is only one part to the entire
test, but that is not the case with any of the multithreaded tests that I've seen. If a test
has three parts, and the first part times out, parts two and three won't execute, but it will
appear that the test ran just fine.

That, and the new code doesn't provide anything for a test that doesn't poll the rw_timeout_expired()
function. So this code is only really useful for the multithreaded tests. If that is the case
then maybe the functionality thould be isolated to just those tests.


> allow thread safety tests to time out without failing
> -----------------------------------------------------
>
>                 Key: STDCXX-536
>                 URL: https://issues.apache.org/jira/browse/STDCXX-536
>             Project: C++ Standard Library
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: trunk
>            Reporter: Martin Sebor
>            Assignee: Travis Vitek
>             Fix For: 4.2
>
>
> The newly added thread safety tests (and possibly some of the existing ones) tend to
run for a long time, consuming a lot of CPU cycles, and sometimes even failing due to a timeout
(currently 300 seconds in nightly builds). It would be useful to provide a mechanism such
as a command line option whereby the tests' runtime could be limited without necessarily causing
them to fail when the amount of time is exceeded. One way to do it would be for each test
to set an alarm in response to this command line option and in handler for the alarm set a
flag that each thread would check at each iteration of its loop to see if it should break.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message