[
https://issues.apache.org/jira/browse/STDCXX-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor updated STDCXX-536:
Severity: Usability
Patch Info: [Patch Available]
Set Severity to Usability and checked
Martin Sebor wrote:
Another option would be to continue testing these sections, but
separate them out into their own tests.
Right. That's the solution I keep ending up with as the most robust
one. The main advantage I see is minimizing the scope of the tested
functionality. The biggest
Travis Vitek wrote:
Martin Sebor wrote:
[...]
We could eliminate some of the overhead due to building
these tests by building just one binary and rigging our test driver
to invoke it two or more times with different options (I like this
feature in and of itself a lot) but I fear there is
Hi Travis,
Can you describe how this all works? I.e., what happens to a test
invoked without the --timeout option when it exceeds the default
295ms timeout? What happens to one that is invoked with the option?
From your comment below it sounds like the solution you implemented
is different from
Ah, maybe there was some miscommunication in our phone conversation on
Friday. When we were talking about this, I mentioned adding a little bit
of code to main for the command line argument stuff, and a little code
to the thread_func to check the flag in each multithreaded test. You
responded
Travis Vitek wrote:
Ah, maybe there was some miscommunication in our phone conversation on
Friday. When we were talking about this, I mentioned adding a little bit
of code to main for the command line argument stuff, and a little code
to the thread_func to check the flag in each multithreaded
Martin Sebor wrote
Travis Vitek wrote:
Whatever timeout period you specify to --timeout-period=N
will be the number of seconds that will elapse before the
_rw_timeout_expired flag will be set to a non-zero value.
[...]
Right. But tests whose threads that don't check the flag will
[
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 [EMAIL PROTECTED]
STDCXX-536
[
https://issues.apache.org/jira/browse/STDCXX-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Travis Vitek updated STDCXX-536:
Attachment: (was: stdcxx-536.patch)
allow thread safety tests to time out without failing
[
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
fixed patch to not use rw_note when timer expires because that
[
https://issues.apache.org/jira/browse/STDCXX-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor updated STDCXX-536:
Fix Version/s: 4.2
Tentatively scheduled for 4.2.
allow thread safety tests to time out without
11 matches
Mail list logo
