QA/Automation/Meetings/120326

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# 315 (US/INTL)
   #         1-800-707-2533 (pin 369) Conf# 315 (US)
   # IRC:    irc://irc.mozilla.org:6697/#automation

General

  • Attendies:
    • Henrik
    • David Burns
    • Dave Hunt
    • Clint Talbert
    • David Guo
  • This meeting:
    • Chair: Cameron Dawson
    • Notes: David Guo

Last Weeks Action Items

  • [CARRY OVER] David Burns: Will Send summary of infrastructure duties/tasks to team
  • [NEW] Clint: come up with goals proposal
  • [NEW] Dave Hunt: document steps for people when they hit a memory spike
  • [NEW] All: respond to feedback requests for pull requests
  • [NEW] All: formulate project and individual Q2 goal ideas and send to Clint

Roundtable

  • TBD.

Goals Overview

Please mark topics which need to be discussed in the meeting as bold

Issues / Blockers

  • No updates

Remote Mechanism to trigger Mozmill tests for Firefox releases (Geo)

  • No updates

CI system for daily and l10n Firefox Builds (Henrik)

  • Dynamic job execution requests per node group has been implemented. Means the Pulse consumer can trigger tests on specific platforms given the config file.
  • Have to find a solution to share shell code between Windows and Mac/Linux without having to duplicate the testruns for those platforms. Possible solution could be something like XShell.
  • Readme has been updated to allow other to dive into the project
  • Investigation of PulseBuildMonitor for easier handling of Pulse notifications

Mozmill 2.0 support for Automation Scripts (Henrik)

  • Received feedback from Henrik - new plan to drop 1.5 support for the new branch of mozmill-automation

Data Validation Method for Mozmill Dashboard (DavidB)

  • Will be finished later today

MemChaser

  • We now support the new GC/CC API by listening to their observer notifications
  • All GC/CC related information is now passed through to the log file and the main module. The widget itself extracts the wanted parts now. Would be a first step for the template support.
  • Log file entries are now individual entries for GC, CC, and memory usage. This was a request from JS devs to better parse the content
  • The widget does show tooltips for all elements now!
  • Circular buffer support will hopefully land soon
  • Still on track with another release around Apr 3rd

Job Page for Community Members (DavidB)

Weekly Blog Posts (Rotating)

Project Updates

Please mark topics which need to be discussed in the meeting as bold

Endurance Tests

Current Work

  • In Progress
    • Framework
    • Tests
  • Landed Recently
    • Framework
    • Tests
  • Backlog
  • Regressions
  • Failing Tests

Discussion Items

Infrastructure

  • Shadow test server
  • Cloud Automation

Case Conductor (Cameron)

  • Working on a name still
  • Finishing up last things for 1.0 at EOQ

Mozmill

Feedback from Firefox Desktop Automation team

  • No updates

Shared Modules

  • No updates

API Refactor

  • No updates

Automation Scripts

  • No updates

Dashboard

  • No updates

Mozmill Crowd

  • No updates

On-demand Testing

  • No updates

Selenium

  • Grid
  • Mobile

Other

  • E.g. JMeter

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] David Burns: Will Send summary of infrastructure duties/tasks to team
  • [CARRY OVER] Clint: come up with goals proposal
  • [CARRY OVER] Dave Hunt: document steps for people when they hit a memory spike
  • [CARRY OVER] All: give feedback to circular buffer pull request ( https://github.com/mozilla/memchaser/pull/31 )
  • [NEW] All: formulate project and individual Q2 goal ideas and send to Clint
  • [NEW] Dave Hunt: assist Geo with the on-demand triggered Mozmill task
  • [NEW] Cam: Finalize a name for 'Case Conductor'
  • [NEW] Geo: Respond with remaining tasks to do for the on-demand projec