Auto-tools/Automation Development/Meetings/130624: Difference between revisions
< Auto-tools | Automation Development | Meetings
Jump to navigation
Jump to search
Line 21: | Line 21: | ||
= Roundtable = | = Roundtable = | ||
* | * Mozmill 2.0 and restart tests | ||
** While working on {{bug|865690}} (I/O port completion) I discovered lots of issues with user shutdown paths | |||
*** Some ways still don't raise an quit-application-requested observer notification which case a bad exit | |||
*** High risk for race conditions when test ends early and timer for userShutdown kicks in later | |||
*** If user restart/shutdown fails we continue to run the next test in the same instance of Firefox | |||
** How do we want to proceed with user restart tests? | |||
*** We might want to desupport the user shutdown feature | |||
*** Or only allow those, which go through the UI (those always send a notification) | |||
*** Normal restarts seem to work fine (at least for me) | |||
= Goals Overview = | = Goals Overview = |
Revision as of 14:55, 24 June 2013
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:
- TBD
- Chair: TBD
- Notes: TBD
Last Weeks Action Items
- [DONE] Henrik - Keep bug tracking in Bugzilla (mozmill-automation scripts)
- [CARRY OVER] Henrik - Start a thread on the public list to collect ideas for the show and tell
Highlights
- [%name%] %highlight%
- New blockers, any updates?
- %new blockers%
- You can find all blockers here: http://bit.ly/Tph0NY
Roundtable
- Mozmill 2.0 and restart tests
- While working on bug 865690 (I/O port completion) I discovered lots of issues with user shutdown paths
- Some ways still don't raise an quit-application-requested observer notification which case a bad exit
- High risk for race conditions when test ends early and timer for userShutdown kicks in later
- If user restart/shutdown fails we continue to run the next test in the same instance of Firefox
- How do we want to proceed with user restart tests?
- We might want to desupport the user shutdown feature
- Or only allow those, which go through the UI (those always send a notification)
- Normal restarts seem to work fine (at least for me)
- While working on bug 865690 (I/O port completion) I discovered lots of issues with user shutdown paths
Goals Overview
Project Updates
Gaia UI (Dave)
- Goals progress:
- TBD
WebRTC (Henrik)
- Goals progress:
- TBD
Softvision Updates
Desktop Automation
- Goals progress:
- TBD
Mobile (Robocop)
- Goals progress:
- TBD
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
- [NEW] %name%: %task%