On 12/3/2013 8:02 PM, Nicholas Nethercote wrote: > 3) Runs on mozilla-central and all trees that merge into it
This is something that Release Engineering needs to fix. You've already got a bug open, so you should touch base with them. > 4) Scheduled on every push This is also RelEng. These both have a capacity impact, but as you said it's on Linux which is where we have the most capacity to begin with. > 6) Outputs failures in a TBPL-starrable format > > Currently the Valgrind builds show up as green, even if there are failures > (https://bugzilla.mozilla.org/show_bug.cgi?id=823787). That needs fixing. > > Again, what code needs to change for this to happen? Who do I need to talk > to? You'd likely need to make changes to the script that does the Valgrind runs, which is currently a shell script (which is horrible). Moving this to a mozharness script would probably make life easier, but also may be significant effort. You CCed a bunch of sheriffs on your original mail, they're best qualified to answer the specific details of this piece. > 11) Easy for a dev to run locally > > We have https://bugzilla.mozilla.org/show_bug.cgi?id=631842 for adding a make > target and/or mach command. I'm not sure if this point is critical? If it > is, > I should be able to do it without too much difficulty, I hope. Primarily this is to make things as simple as possible for when someone pushes code that causes a failure in a test suite. I think we can easily add a mach command that executes this command, since it's just running "make pgo-profile-run" with Valgrind attached. -Ted _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
