ReleaseEngineering/Mozharness/28-Mar-2012

From MozillaWiki
< ReleaseEngineering‎ | Mozharness
Revision as of 17:49, 28 March 2012 by Jhammel (talk | contribs) (→‎Roundtable: note jetperf/talos discussion)
Jump to navigation Jump to search

Details

  • Every other Wednesday - 1:00pm Pacific, 4:00pm Eastern
  • Dial-in: Audio-only conference# 99021
    • People with Mozilla phones or softphones please dial x4000 Conf# 99021
    • US/Toll-free: +1 800 707 2533, (pin 4000) Conf# 99021
    • US/California/Mountain View: +1 650 903 0800, x4000 Conf# 99021
    • US/California/San Francisco: +1 415 762 5700, x4000 Conf# 99021
    • US/Oregon/Portland: +1 971 544 8000, x4000 Conf# 99021
    • CA/British Columbia/Vancouver: +1 778 785 1540, x4000 Conf# 99021
    • CA/Ontario/Toronto: +1 416 848 3114, x4000 Conf# 99021
    • UK/London: +44 (0)207 855 3000, x4000 Conf# 99021
    • FR/Paris: +33 1 84 88 37 37, x4000 Conf# 99021
    • Gmail Chat (requires Flash and the Google Talk plugin): paste +1 650 903 0800 into the Gmail Chat box that doesn't look like it accepts phone numbers
    • SkypeOut is free if you use the 800 number
  • irc.mozilla.org #ateam ? for backchannel
  • vidyo: Aki's room, 9021

Landed

In Progress

  • aki can start on these next week

On the Horizon

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

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.

  • 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