I care about testing Firefox under valgrind, but if the valgrind builds are red and have been red for a long time there's no point in continuing to run them to see that they're still red.
They've been red for a long time partially because the Valgrind version wasn't upgraded as Firefox was developed. If I'm not wrong the Valgrind version we're using on tbpl is 3.6.x (released late 2010 / early 2011).
(e.g. --smc-check=all-non-file which was first introduced in 3.7.0 is recommended to run Firefox now with all the JITs that we have in Spidermonkey. There are also a bunch of false positive fixes in the newer Valgrinds.)
Bug 750856 is the bug mentioning the upgrade in Valgrind (which also permits Valgrind running on Mac machines, should it be implemented in the future)
-Gary _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
