QA/Automation/Meetings/140127

From MozillaWiki
< QA‎ | Automation‎ | Meetings
Jump to: navigation, search

previous meeting | Meetings | next meeting »

Dial in

 # When:     Every Monday at 8:45am PDT/PST
 # Vidyo:    https://v.mozilla.com/flex.html?roomdirect.html&key=PGtLpx3XQGJz
 # Phone:    650-903-0800 or 650-215-1282 x92 Conf# 9654 (US/INTL)
 #           1-800-707-2533 (pin 369) Conf# 9654 (US)
 # IRC:      irc://irc.mozilla.org:6697/#automation
 # IRC logs: http://irclog.gr/#browse/irc.mozilla.org/automation

General

  • Attendees:
  • Chair: Andreea
  • Notes: Cosmin

Last Weeks Action Items

  • [CARRY OVER] [Henrik] Update the 'How to handle a meeting' wiki page for recording and publishing the video
  • [CARRY OVER] [Andrei] Check Mozmill Automation how Mercurial returns the exit code for all platforms in case 'hg pull' fails (see github mozmill-ci issue under blockers)
    • I've had another look at this issue.
      • This has been solved by Dave by forcing to pull the branch with `-R`
      • What's needed here is to back out Dave's patch and run exhaustive testruns in Jenkins in hope to reproduce the issue. Once done we should check all possibleways it can fail.
      • Since this will be time-consuming and we're really time-constrained right now, I'll create a new github issue or bugzilla bug for us to investigate this at a later point in time.
      • We our current pressing goals there is really no time to spend on this right now.

Highlights

Roundtable

  • [henrik] Faster processing of reviews for Mozmill
    • Please add f? for Henrik if a new feature or an API change has to be implemented
    • Ask final review from Henrik after you came to an internal agreement (r+) in the SV team
    • I might want to ask Nils to help me in reviewing code for certain repositories
  • [henrik] Tests for special Firefox updates - Anthony, how often will those happen?

Goals Overview

Project Updates

Mozmill (Henrik)

  • We are closer to a Mozmill 2.0.4 release - we landed two major blockers by end of last week, and the mozrunner refactor; two more bugs to follow

WebRTC (Nils)

  • TBD

Softvision Updates

Desktop Automation

  • Goals progress:
  • Daniel is in ramp-up, working on some mentored bugs (new metro test, security UI library)
  • Andrei updated all nodes with latest updates
  • We worked on metro, the dashboard, running a testrun on ci, UI lib and new tests
  • Resolved Fixed:
    • bug 795398 - Mozmill test to check that MD5 hash signatures are no longer accepted
    • bug 961842 - Update all nodes for latest OS, Flash, and Java updates
    • bug 960976 - Disable pref extensions.getAddons.cache.enabled for Firefox and MetroFirefox to not interfere with AMO statistics
  • Working on:
    • Andreea
    • Andrei
      • bug 835739 - Move element specifications for find bar into lib/toolbars.js
      • mozmill-dashboard - Add Top Failures feature to remote testrun
      • bug 908649 - Refactor lib/downloads.js replacing the nsiDownloadManager backend with the new Downloads.jsm implementation
      • bug 856084 - Test failure "The cookie has been removed - got 'false'" in /testPreferences/testRemoveCookie.js
    • Cosmin
      • bug 948912 - No results on any testruns for Mac OS X 10.6.8 are appearing in the dashboards
      • bug 962011 - l10n testruns don't run on mac
    • Mario
      • bug 851502 - Create an Endurance test to measure html5 video memory use
      • bug 924077 - Write mozmill metro test for opening and closing tabs
      • bug 962514 - Test failure 'client process shutdown unsuccessful'

Personal Status

For the personal status please check the weekly status updates:

Meeting Notes

The meeting notes for this meeting can be read in the following etherpad:

If you missed the meeting you can also watch it in our archive.

Action items

  • [CARRY OVER] [Henrik] Update the 'How to handle a meeting' wiki page for recording and publishing the video
  • [NEW] [Henrik] to investigate that testers are back on beta channel and not on release. See how to help qa the next 6 weeks with update tests so that beta testers are really back on the beta channel and are not stuck on the release channel. If we can test this on a majority of locales this would be helpfull and help qa stop running these tests manually.
    • RC builds are pushed to beta testers and RC users to get more crash stats and get more informed decisions regarding respining. Due to this manual qa need to run update tests every release and these are very time-consuming
  • [NEW] [Andrei] Add an issue on Git and add it in the backlog for: Check Mozmill Automation how Mercurial returns the exit code for all platforms in case 'hg pull' fails (see github mozmill-ci issue under blockers)
Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Automation/Meetings/140127&oldid=911929"