On 07/22/2011 09:04 AM, Graydon Hoare wrote:
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.

rustc is not currently valgrind clean. There are a few invalid memory accesses that Patrick has patches for, but beyond that there are leaks as well.

_______________________________________________
Rust-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/rust-dev

Reply via email to