stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Travis Vitek <>
Subject Re: [jira] Updated: (STDCXX-536) allow thread safety tests to time out without failing
Date Tue, 06 May 2008 00:35:17 GMT

Martin Sebor wrote:
> Travis Vitek wrote:
>> Are you talking about modifying the nightly build infrastructure so that
>> it will invoke a test several times with different command line
>> arguments to run the test differently, or are you thinking about having
>> the test invoke itself with different arguments or something? I don't
>> think any option other than the first will work.
> The former. I'm envisioning changing the exec utility (which runs
> the tests) to look for some "command" file corresponding to each
> test from which it would figure out how many times to run it and
> with what options. If the file didn't exist exec would run the
> test the same way it does now.

This seems quite a bit more complicated than what was originally proposed.
It involves changes to the test infrastructure in addition to modifications
to the tests themselves, and probably the build result reporting code.

Martin Sebor wrote:
> This approach could even be extended to compiling and linking
> certain tests with special options, or to implement negative
> testing, i.e., to exercise the ability of the library to reject
> invalid programs.

I think that being able these types of testing might be useful.
Unfortunately I see this as being a very complicated way to do what we claim
we want.

Martin Sebor wrote:
> It would even let us deal with the increasing
> disk space problem by compiling and linking each test on demand
> just before running it and then immediately deleting it to free
> up disk space.

It seems that we could already do this with the existing makefile. The
run_all rule would just have to be modified to build the executable before
it is run and clean it up afterward. That doesn't seem like it would be
terribly difficult.

I've gone back to read through the previous messages in this thread and I
don't understand why we cannot just use a single timeout per
rw_thread_pool() call. If a test has 3 sections (as most of them do), the
timeout would apply to each section independently. We could set the default
soft limit to 30 seconds or so, and then such a test would finish in
approximately 90 seconds.

I think that is what you originally intended, but I got off track at some
point and made everything all confusing.

View this message in context:
Sent from the stdcxx-dev mailing list archive at

View raw message