On 22/07/2011 6:32 AM, Rafael Ávila de Espíndola wrote:
On 11-07-22 5:00 AM, Marijn Haverbeke wrote:
The failure at [1] seems to be non-deterministic -- the patch I
applied didn't touch anything low-level enough to cause a segfault,
and the next patch I pushed 'fixed' it, although it didn't revert the
first patch or even touch anything remotely related (it changed a
test, not the one that was failing). Any ideas what this might be?
No, but I have seen similar issues, both on the Linux and Windows bots.
Does anyone knows if the linux bots runs only the tests on valgrind? Maybe
we could build stage3 with it too...
Linux does the tests only under valgrind, not the compiler. We can
modify it.
My guess is the failure was a timeout, as cycle time was 2h3m. As to why
it spun for 2h, I do not know. It's running in a crappy VM shared with
the linux box. It's possible the machine just got swappy or such. We use
an *awful* lot of memory building these days. I'll take a closer look at
cycle time when I'm in the office. Something's off.
I continue to await updates on our more-official tinderboxes.
-Graydon
_______________________________________________
Rust-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/rust-dev
