Nicholas Nethercote writes: > - When a job times out, the output produced by Valgrind is > usually chopped off in the middle of a line. In fact, it's > often chopped off in the middle of a line that would have been > produced by a single write() system call. So it feels like the > test harness is somehow abruptly stopping its recording of the > output.
Yes, sounds like all processes in the test are being killed. Most tests have a shorter time out to kill with signals that generate stacks, before this higher level time out kicks in. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
