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

Revision as of 01:04, 4 April 2012

(jhammel) - iterate on different option naming
- https://bugzilla.mozilla.org/show_bug.cgi?id=738478#c19
(jhammel) - populate people.m.o with required packages
- http://people.mozilla.com/~jhammel/pypi/
(jhammel) - move common code from talos_script to mozharness.mozilla.talos
- still open
(aki) - help jeff with talos error lists
- https://bugzilla.mozilla.org/show_bug.cgi?id=738478#c15
(aki?) - file bug to improve virtualenv support (default pypi server)
- https://bugzilla.mozilla.org/show_bug.cgi?id=740147 , seems to be blocked by py27

aki can start on these this week
- bug 720436 - Generalize the firefox fetching pattern from peptest.py
- bug 650890 - remote talos

(ateam+releng) bug 713055 - talos on mozharness in production (q2)
(jhammel) bug 701506 - python package webserver
(jlund) bug 740142 - Firefox l10n. I'd like to make these similar to the Fennec l10n solution, and help users create repacks locally..
bug 650881 - remote unittests
bug 650880 - desktop unit tests

@@ 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 ==