stdcxx-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Sebor (JIRA)" <>
Subject [jira] Commented: (STDCXX-536) allow thread safety tests to time out without failing
Date Fri, 09 May 2008 16:02:55 GMT


Martin Sebor commented on STDCXX-536:

I don't have any specific issues in mind that should cause problems in our case. It's possible
that the {{alarm()}} solution will be perfectly safe in the limited set of situations that
we have to worry about, even if it isn't robust enough to be completely general. But experience
has taught me that programs that mix threads and signals do tend to run into unanticipated
problems, often due to portability issues, so I'm simply trying to see if there's a better,
more general alternative. If not I guess we'll just have to trust we'll be fine and not push
it too far in the future (e.g., when we implement the [C++ Multi-threading library|]).

> allow thread safety tests to time out without failing
> -----------------------------------------------------
>                 Key: STDCXX-536
>                 URL:
>             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.

View raw message