ReleaseEngineering/Mozharness/23-Oct-2013

From MozillaWiki
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Details

  • Every other Wednesday - 1:00pm Pacific, 4:00pm Eastern
  • Dial-in: Audio-only conference# 9354
    • People with Mozilla phones or softphones please dial x4000 Conf# 9354
    • US/Toll-free: +1 800 707 2533, (pin 4000) Conf# 9354
    • US/California/Mountain View: +1 650 903 0800, x4000 Conf# 9354
    • US/California/San Francisco: +1 415 762 5700, x4000 Conf# 9354
    • US/Oregon/Portland: +1 971 544 8000, x4000 Conf# 9354
    • CA/British Columbia/Vancouver: +1 778 785 1540, x4000 Conf# 9354
    • CA/Ontario/Toronto: +1 416 848 3114, x4000 Conf# 9354
    • UK/London: +44 (0)207 855 3000, x4000 Conf# 9354
    • FR/Paris: +33 1 84 88 37 37, x4000 Conf# 9354
    • 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, 354

Previous action items

Project tracking

Gaia Unit tests (jgriffin)

Stabilize vcs-sync (aki)

Mozpool / Mozharness for Android Pandas (kmoir)

Desktop l10n (mgerva)

run_command() timeouts (jgriffin)

metro talos (jlund)

Android x86 tests (armenzg, callek)

Blob uploads (mtabara)

Static rooting analysis builds (sfink)

Firefox desktop builds (jlund)

    • maybe not a roundtable discussion but looking to have an informal talk about handling various configs for branch, platform, build type (pgo, debug, etc), and production type (staging, preprod, etc). This is a maintenance/scaling question that I am trying to tackle early.

Gaia integration tests (gaye)

Next

  • in-harness parallelization
  • jetperf
  • context lines
  • mozharness try

Roundtable

  • (aki) two years of mozharness meetings
  • (aki) irc #mozharness ? mozilla.dev.mozharness/mozilla.tools.mozharness newsgroup/email list ?
    • mozilla.tools as a possibility; #mozharness now exists
  • (aki) do we need to discuss mozbase, specifically mozdevice?
    • freezing api?
    • checking a static version of mozdevice into mozharness ?
    • creating a mhmozdevice package that can live in the same venv?
    • avoiding two virtualenvs

Action Items

  • mozdevice bustage:
    • immediate fix is probably adding in-tree mozfile before mozdevice in the virtualenv_modules
    • move to using the two-pass mozbase install method for mozharness in general (in TestingMixin?)
    • longer term we could reduce mozharness calls to mozdevice to high-level actions, and keep the logic in mozdevice or another module that wraps mozdevice
    • want to avoid two virtualenvs; if we fork mozdevice we probably want to make that as a conscious decision.

Done

  • B2G panda builds
  • B2G otoro builds
  • B2G unagi builds
  • B2G desktop multilocale
  • B2G device multilocale
  • mozpool mozharness integration
  • marionette
  • b2g emulator-with-codecs testing
  • ash-mozharness
  • mozharness production branch
  • android signing-on-demand
  • b2g 1.x.x support
  • mozharness desktop unittests
  • multiple config file support
  • generic retry()
  • mozharness CI
  • b2g gaia smoketests on pandas
  • additional b2g device builds (inari, leo, hamachi/buri)
  • get rid of b2g snapshots
  • mozharness nosetests broken on windows
  • b2g crash symbols
  • servo builds
  • gaia.json autocommits
  • full emulator tests
  • resource monitoring, part 1
  • desktop talos
  • cpp unittests
  • beagle hg-git conversions
Retrieved from "https://wiki.mozilla.org/index.php?title=ReleaseEngineering/Mozharness/23-Oct-2013&oldid=735629"