besides the current GUMP problem (which yes, I created by having gump try and run the tests, and will fix), http://cvs.apache.org/builds/gump/latest/excalibur-monitor.html
I get:
test:
<snip/>
Total time: 7 seconds
this is on an NTFS filesystem. I'll try and find more time for debugging it.
The problem is that we have one thread that modifies the file, while the active monitor is poling it. If the monitor doesn't detect the change within ~1-10 seconds (I can't remember what it was set to), then the assertion fails.
The problem I had when writing this test is that in accordance with Murphy's law, the monitor would notice the change after the timeout. We could wait indefinitely, but then what happens if it is legitimately broken?
Times where it was failing to respond in a reasonable time coincided with heavy disk access--which includes memory swapping and build times.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
