ReleaseEngineering/Mozharness/04-Apr-2012: Difference between revisions

ReleaseEngineering/Mozharness/04-Apr-2012 (view source)

1,377 bytes removed , 4 April 2012

Confirmed users

4,971

edits

@@ Line 40: / Line 40: @@
 == Roundtable ==
-My (jhammel) priorities are to get bug 738478 unblocked so I can work
-on jetperf (first bug 729205)
-Issues:
-* What to do about PerfConfigurator options?
-** --perfconfigurator_options -a,ts,-e,`which firefox`,--result_url,file://...
-*** would make jetperf.py difficult, e.g. results_url
-** use the options we have, make the help e.g. "--activeTests option for PerfConfigurator"
-*** not very helpful
-** other ideas?
-I really want configuration that makes it easy for me (and presumedly everyone
-else) to run.
-* Firefox fetching:
-** aki is taking bug 720436, looks like: https://wiki.mozilla.org/ReleaseEngineering/Mozharness/28-Mar-2012#In_Progress
-** should we block on this?
-* Dependencies: what should we do in the immediate term?
-** "pypi" on p.m.o/~jhammel/pypi ?
-** list verbosely? (e.g. using a tool to gather them?)
-* Error checking
-** I'm making it a priority to make our error checking better in Talos
-** can we land bug 738478 without listing error messages?
-*** follow-up bug
-*** otherwise, this might take some time while I figure out what to do here
-* Alternatively, we can have jetperf (and conceivably talos remote) not inherit from talos_script:Talos. While I think this is the wrong move, if it avoids the conflicts here maybe it is expedient.
-It is my basic belief that if this patch is better than what we have now we should take it and build on it.
 == Action Items ==