QA/Automation/Meetings/120917

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

previous meeting | Meetings | next meeting »

Dial in

 # 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

General

  • Attendees:
    • TBD
  • This meeting:
    • Chair: Henrik
    • Notes: TBD

Last Weeks Action Items

  • [NEW] Clint: Follow up with IT on status of the new ESX cluster
  • [NEW] Clint: Demo mochitest browserchrome at next meeting
  • [DONE] Dave: Revisit all memory leak issues using tinderbox builds on CI
  • [DONE] Henrik: Follow up with MozCamp attendees regarding automation contributions
  • [ON TRACK] Henrik: Talk to Jason from iriscouch to enable ES backend
    • No reply from IrisCouch support yet
  • [DONE] Henrik: Follow-up on MozCamp Asia for participation
    • Will happen November 17-18th, but no Wiki pages created yet

Highlights

  • [%name%] %highlight%

Q3 2012 Goals Overview

Blockers

  • bug 772831 - [HELPDESK] - ESX machine hosting vc1.qa.mtv1.mozilla.com seems to be too unstable
  • bug 787252 - Regenerate a SSLCertificateFile and SSLCACertificateFile for ssl-dv.mozqa.com

Issues

  • bug 761564 - Memory leaks in Mozmill Python code which keeps references around and never completely releases the Mozmill object
  • bug 774892 - Unable to type in Firefox if it's started with focusmanager.testmode enabled on Linux
  • bug 702605 - Allow interaction events to be injected into the Event Queue
  • bug 767348 - Memory consumption shows an ascending trend on Nightly/Win 6.1 x64
  • bug 764823 - Memory spike discovered by endurance tests on Nightly Linux and Mac between June 12 and 13
  • bug 773632 - High results on mozmill endurance test on Mac 10.7.4_x64 since Jul 5

Roundtable

  • Do we want to remove the Mozmill IDE from the extension for Mozmill 2.0? (bug 791625
  • Can we start to assign team members as point of contact for our frameworks and tools?
  • Do we want to have a separate section for other frameworks like the ones Rob covers?

Presentation / Demo

  • [clint] Browser Chrome tests

Triage

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:

Action items

  • [CARRY OVER] Henrik, Rob: Continue follow-up from MozCamp attendees
  • [NEW] All: Assign team members for point of contact for frameworks and tools