Do you have a stacktrace of where in BaseTokenStreamTestCase that it hit? We refactored the asserting here, to always test with a single thread *first*, then with multiple threads.
So if you are failing in the multithreaded part, it means you have a thread safety issue... (as long as this part of the base test class is working, and i hope it still is, i havent seen anything crazy to indicate otherwise, and i've been in TestRandomChains for a few hours this week) On Fri, Mar 21, 2014 at 1:57 PM, Benson Margulies <[email protected]> wrote: > I'm fighting with a test that uses the random analysis chain testing. > It does not repro when I pass in the usual collection of -D's. I think > that the reason is to do with threads; the failure is always on a big > multicore build machine. > > Are there any more of those Carrot control -D's that change how many > threads are in the act? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
