Hi, >>>>> "A" == Army <[EMAIL PROTECTED]> wrote:
A> When I run this test against a local codeline, I seem to be seeing intermittent A> failures because two lines in the output file are printed out of order. <snip> A> All of that said, I think I've found the cause of the problem (System.err and A> System.out are overlapping), but I'm not sure what the best solution is. It A> seems like changing the "shutdown ok", "finished successfully", and "Test A> errorStream starting" (just to be safe) messages to use System.err would solve A> the problem, but that's not a very intuitive solution. A better fix would be to A> somehow change the 'default error stream' (for cases when an error A> file/method/field doesn't exist) to be System.out--but is that even possible?? A> A> If anyone has any input here, please do speak up (it's quite possible I'm A> missing something). Otherwise, though it's not very intuitive, we might need to A> change the above-mentioned messages to all print to System.err in order to avoid A> the intermittent diff(s)... This seems like the symptom Kathey observed once before she checked this one in for me. I never saw it during my testing of this test case, and we concluded (obviously too quickly) that the test case was ok. I'll look into it again - thanks for catching this one! Not sure how to best solve this given the test infrastructure.. so please chime in! Dag
