Re: [reSIProcate] testThreadIf sensitivity?

[Scott Godin <sgodin@xxxxxxxxxxxxxxx>]

I think expecting the thread to end within 20ms is pretty aggressive for slow/busy systems.  I think we can just change this value to something higher - say 100 or 200ms.

Scott

On Tue, Dec 17, 2013 at 9:34 AM, Daniel Pocock <daniel@xxxxxxxxxxxxx> wrote:

Build 483 failed in testThreadIf (log link below), maybe this is too
sensitive for use in cloud-based unit testing?

We could move some of these thresholds out to a header file and keep
alternate values (or an alternate header file) for travis builds

Does anybody else have any suggestions about it?


finished many-thread test
1387281496265
Stopping thread at: 1387281497221
Stopped at: 1387281497221
53
lt-testThreadIf: testThreadIf.cxx:123: int main(): Assertion `j - t <
20' failed.
/bin/bash: line 5: 28224 Aborted                 ${dir}$tst
FAIL: testThreadIf





https://api.travis-ci.org/jobs/15579286/log.txt?deansi=true




_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel