Mobile/Testing/10 19 11: Difference between revisions

 
(12 intermediate revisions by 2 users not shown)
Line 2: Line 2:


* Mossop to work with clint and joel to figure out a plan for getting testing stood up on the Native UI
* Mossop to work with clint and joel to figure out a plan for getting testing stood up on the Native UI
** success!
*** everthing is running
*** ts and twinopen pass which don't use fennec chrome
*** mochitest plain passes
*** everything else passes
* bear to file bugs for getting nightlies and nightly updates for birch
* bear to file bugs for getting nightlies and nightly updates for birch
** bugs filed
* [carried] bear will follow up with Armen to figure out his objection to a an email notification about no talos results {{bug|689625}}
* [carried] bear will follow up with Armen to figure out his objection to a an email notification about no talos results {{bug|689625}}
** bear will take over bug
* [carried] joduinn to start a discussion of process in {{bug|689625}}
* [carried] joduinn to start a discussion of process in {{bug|689625}}
* [carried] jmaher, gbrown & blassey to generate a set of minimum requirements for running tests on android
* [carried] jmaher, gbrown & blassey to generate a set of minimum requirements for running tests on android
Line 13: Line 20:


== Rel Eng ==
== Rel Eng ==
* [http://is.gd/ZEOCi7 android_tier_1]
* [https://wiki.mozilla.org/ReleaseEngineering/Mozharness/12-Oct-2011 Mozharness ]
* [https://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-birch-android/ birch nightlies]
* [https://wiki.mozilla.org/Mobile/Notes/19-Oct-2011#Release_Engineering Mobile Mtg Notes]
== A Team ==
== A Team ==
* [[https://docs.google.com/spreadsheet/ccc?key=0ArS97F99-BEZdHdxRFNjcFIwWnk5RFROck5pMXo3WXc&hl=en_US#gid=0 failures]] spreadsheet per test type and failure type
* [[https://docs.google.com/spreadsheet/ccc?key=0ArS97F99-BEZdHdxRFNjcFIwWnk5RFROck5pMXo3WXc&hl=en_US#gid=0 failures]] spreadsheet per test type and failure type
Line 29: Line 41:


= Round Table =
= Round Table =
* should we disable or hide J1 and R2?


= Action Items =
= Action Items =
* bear to take {{bug|689625}} from armen
* joel to disable J1 and R2
* [carried] joduinn to start a discussion of process in bug 689625

Latest revision as of 17:22, 19 October 2011

Previous Action Items

  • Mossop to work with clint and joel to figure out a plan for getting testing stood up on the Native UI
    • success!
      • everthing is running
      • ts and twinopen pass which don't use fennec chrome
      • mochitest plain passes
      • everything else passes
  • bear to file bugs for getting nightlies and nightly updates for birch
    • bugs filed
  • [carried] bear will follow up with Armen to figure out his objection to a an email notification about no talos results bug 689625
    • bear will take over bug
  • [carried] joduinn to start a discussion of process in bug 689625
  • [carried] jmaher, gbrown & blassey to generate a set of minimum requirements for running tests on android
  • blassey to follow up with js team on bug 691073

Status reports

Dev team

no updates

Rel Eng

A Team

  • [failures] spreadsheet per test type and failure type
    • 8.77% orange, 12% total failure
  • do we continue to run browser-chrome?
  • can we hide jsreftest-1 and reftest-2 from the default view? those account for 57% of the oranges
  • specialpowers is almost done, more tests should start coming online soon
  • landed manifest file for android tests, releng needs to deploy the buildbot changes in bug 694741
  • when we will get stackwalk in automation bug 693352
  • jsreftest crash is still showing up, we have a fix that helps out; bug 691073
  • rss for talos collection is starting to come together bug 685632
    • WIP patches in place
  • native UI tests- we have mochitests working;
    • need to update pageloader and related talos tests to work in nativeUI
    • need to get reftests going

Round Table

  • should we disable or hide J1 and R2?

Action Items

  • bear to take bug 689625 from armen
  • joel to disable J1 and R2
  • [carried] joduinn to start a discussion of process in bug 689625