[
https://issues.apache.org/jira/browse/STDCXX-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Travis Vitek updated STDCXX-536:
--------------------------------
Attachment: stdcxx-536.patch
2007-09-10 Travis Vitek <
vitek@...>
STDCXX-536
rw_timeout.h: New file declares timeout functions used by
tests.
opt_timeout.h: New file declares timeout functions used by
the test suite driver.
opt_timeout.cpp: New file defines timeout functions used by
the test suite driver.
driver.cpp (rw_vtest): setup new command line options,
enable and disable alarm for timeout.
22.locale.messages.mt.cpp (thread_func): use timeout to
let test threads exit early.
> 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
>
> Attachments: stdcxx-536.patch
>
>
> 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.
