stdcxx-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Lemings (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (STDCXX-536) allow thread safety tests to time out without failing
Date Fri, 09 May 2008 16:22:55 GMT

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

elemings edited comment on STDCXX-536 at 5/9/08 9:22 AM:
-------------------------------------------------------------

I agree with Martin's concerns on mixing threads and signals.  I would suggest using a messaging
framework; it would be safer but would require even more infrastructure.  As a starter for
resolving this issue however, we should try Travis' approach since it most likely better than
the current paradigm.

      was (Author: elemings):
    I agree with Martin's concerns on mixing threads and signals.  I would suggest using a
messaging framework; it would be safer but would require more infrastructure.  As a starter
for resolving this issue, we should try Travis' approach since it most likely better than
the current paradigm.
  
> 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: 4.2.0
>            Reporter: Martin Sebor
>            Assignee: Travis Vitek
>             Fix For: 4.2.2
>
>         Attachments: stdcxx-536.patch
>
>   Original Estimate: 3h
>          Time Spent: 4h
>  Remaining Estimate: 0h
>
> 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