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.
hmm. I have an athlon XP 1800, with 512MB DDR333, jdk1.4.1, UDMA133 7200RPM disk, and pretty much tweaked for performance, running almost nothing but the test, and it still fails. I wonder what's wrong :D
- LSD
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
