On Thu, Dec 12, 2013 at 9:48 AM, Nicholas Nethercote <n.netherc...@gmail.com> wrote: >> >> Unfortunately, on December 5th, just before the changes were enabled, >> something >> else happened that caused the Valgrind jobs to start timing out all the time. >> This is being tracked in https://bugzilla.mozilla.org/show_bug.cgi?id=948145. > > I now have a loaner build slave on which I can reproduce the problem. > All indications are that the "Quitter" extension, which the > pgo-profile runs use to quit the browser, is not loading properly -- > there's a "Quitter is not defined" error message. As a result, > Firefox never quits, and the run hangs.
I tracked this down to one of the Quitter files being a symlink with a relative path, and that path was going awry when the file was copied elsewhere within the chroot that the tests run in on the build slaves(!) And by the time I worked this out, glandium had inadvertently fixed the problem by landing an unrelated patch that happened to change that symlink to one with an absolute path. Weird, but at least the Valgrind builds are working again. Nick _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
