947
edits
ReleaseEngineering/Mozharness/28-Mar-2012: Difference between revisions
ReleaseEngineering/Mozharness/28-Mar-2012 (view source)
Revision as of 17:49, 28 March 2012
, 28 March 2012→Roundtable: note jetperf/talos discussion
(→In Progress: update dependency) |
(→Roundtable: note jetperf/talos discussion) |
||
| Line 26: | Line 26: | ||
== Roundtable == | == 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 | |||
== Action Items == | == Action Items == | ||