FxOS/Cross Functional/Meetings/2014-07-15
From MozillaWiki
Contents
Schedule Updates 07/15
- Latest (updated with scheduling, auto uplift queries, etc.):
- Current engineering focus, in priority order:
- 1.3 >> 1.3T >> 1.4 >> 2.0 >> 2.1
- https://wiki.mozilla.org/Release_Management/B2G_Landing#Work_Order
- Repos look like:
- mozilla-central (Nightly): gecko34 and B2G v2.1
- mozilla-b2g32_v2_0: gecko32 and B2G v2.0
- mozilla-b2g30_v1_4: gecko30 and B2G v1.4
- mozilla-b2g28_v1_3: gecko28 and B2G v1.3
- Upcoming Deadlines:
- June 6: Feature Landing - Release 2.0
- For triage queries see:
Previous Actions
- jgriffen will propose that we merge this meeting with the B2G engineering meeting next week.
- Engineering meeting cancelled this week. Will bring this up in two week's time.
- lmandel will send an announcement about the change in meeting time (hold for a week until jgriffen speaks follows up about merging this meeting with the B2G engineering meeting
- On hold until jgriffen's action above is complete.
- lmandel to review 1.4 approval process for 1.3T, slowing devs down, not providing a lot of value
- Not sure exactly how devs are being slowed down. Most 1.4 work should follow blocking process at this point.
- jgriffin will speak with the perf team to ensure they're ok with shifting automation to 256Mb config
Roundtable
Group Updates
RelMan (lmandel, bajaj)
- 1.3 and 1.3T blocking flags have been disabled
- 2.1 scope review happening today
- (bajaj) Who is on point for merge day from releng ? aki will be
QA (Jason/nhirata)
Reporter: nhirata updated 7/15; jsmith on PTO this week, 2 work weeks happening; qa on lower resources this week
- Discussion on email : 256 mem flame testing and whether or not, it's an engineering resources strain or if it's worth the action.
- build 256 mem variable was discussed this morning in the gaia meeting (bug 1024692)
- gallery has a build config variable for 256 : https://github.com/mozilla-b2g/gaia/commit/65ba1cbd2660b770263e6053ff70648843ff7b17#diff-bf3640ad16d676a2b3167a40a52d254fR61
- GAIA_MEMORY_PROFILE=256 when building gaia for 2.0
- camera for 2.0 is hardcoded so the variable does not get affected : https://github.com/mozilla-b2g/gaia/commit/65ba1cbd2660b770263e6053ff70648843ff7b17#diff-ac912d18a26033808a43317f3bd095f9R10
- 1.4
- QA Wanted, smoketesting, and Dolphin-specific test run support
- 48/48 smoketests passing, no blockers (Dolphin 256 MB)
- 14 open blocking bugs : http://mzl.la/1mdZPZu
- 17 1.4? nomed bugs : http://mzl.la/1qDrWW5
- 2.0
- QA Wanted, smoketesting, and full test run support
- 61/62 smoketests passing,3 blockers (Flame 512 MB) on the same smoke test
- [B2G][Everything.me]E.me apps are not displayed and cannot be added to the homescreen after OTA
- [B2G][Settings]SIM not detected after OTA
- https://bugzilla.mozilla.org/show_bug.cgi?id=1038289
- possible caf issue.
- [B2G][OTA] Smart collections are not displayed after OTA 1.3 to 2.0
- https://bugzilla.mozilla.org/show_bug.cgi?id=1037556
- patch in bug
- Loc Run finished : Theo Chevalier sent out an email with the results:
- 2nd round will begin on July 31st.
- Bugbash for flame 273Mb that was planned for this week is pushed to next week: July 24th
- 2.0 Exploratory Test Run against 273MB being currently done
- 2 testers on FMD exploratory testing
- QA Plan to get 273 MB Flame under control
- Part 1 - Sanity Tests (~10 tests) + 2 hours daily exploratory testing by major area on a per day basis (M - Comms, T - Media, W - System, TR - Productivity, F - Misc) on 273 MB Flame
- Exit Criteria - Green Sanity Tests for 3 Days
- Part 2 - Manual Smoke Tests (~44 tests) on 273 MB Flame
- Exit Criteria - Green Smoke Tests for 3 Days
- Part 3 - All testing migrated to 273 MB Flame
- Bug Query - http://mzl.la/1kxNjEv
- Part 1 - Sanity Tests (~10 tests) + 2 hours daily exploratory testing by major area on a per day basis (M - Comms, T - Media, W - System, TR - Productivity, F - Misc) on 273 MB Flame
- 2.1
- QA Wanted & smoketesting support
- 60/63 smoketests passing, 2 blockers (Flame 512 MB)
- [B2G][Clock]Alarms do not go off when triggered. Timer alerts are also affected
- https://bugzilla.mozilla.org/show_bug.cgi?id=1037079
- patch in bug
- [1.4 => 2.0] Wi-Fi networks are erased after an OTA update
- [B2G][Clock]Alarms do not go off when triggered. Timer alerts are also affected
RelEng (aki, catlee)
Tracking wiki page: https://wiki.mozilla.org/User:Asasaki:B2GBuilds
- ai: aki - find someone to take this meeting (or Thursday, depending on scheduling)
- fota flame https://bugzilla.mozilla.org/show_bug.cgi?id=1036835
- changing from ota to fota caused nightly bustages across all trees; we probably need developer-side changes to enable
- ai: aki to file dev bug
- changing from ota to fota caused nightly bustages across all trees; we probably need developer-side changes to enable
- (wontfixed) darwin emulator builds are a timesink https://bugzilla.mozilla.org/show_bug.cgi?id=905742
- (finishing up) automation for other merge day tasks: https://bugzilla.mozilla.org/showdependencytree.cgi?id=1003346&hide_resolved=1
- new b2g32_v2_0 branch coming this week, will go live monday
- new gaia v2_0 l10n repos created, will push latest strings monday
- (kmoir, in progress) c3.[x]large pool: https://bugzilla.mozilla.org/show_bug.cgi?id=1031083
A-team (jgriffin)
Q3 Goals: https://wiki.mozilla.org/Auto-tools/Goals/2014Q3
Complete
- We've started running perf test on Flames on 2.0/aurora
- Change perf runs to low-memory Flame for 2.0, but waiting for https://bugzilla.mozilla.org/show_bug.cgi?id=1036670 to be fixed
- Added support for Marionette tests that restart with a given set of prefs for Loop
Problems
- gaia-integration hidden on TBPL due to frequent intermittents; kgrandon/julienw investigating
In progress
- Gaia-integration tests on-device
- Ahal has most of them working locally; now needs to land patches in several repos:
--> https://github.com/mozilla-b2g/mocha-socket-reporter --> https://github.com/mozilla-b2g/marionette-socket-host
- aims to have these working on Flames by July 21
- Certification Suite
- Aiming to have a 1.4-compatible release by July 25
- Investigating the scope of work needed to make the suite compatible with non-phone devices
- Mulet
- builds available on fig and try: https://bugzilla.mozilla.org/show_bug.cgi?id=997096
- starting work on greening up tests: https://bugzilla.mozilla.org/show_bug.cgi?id=1027242
- working on getting OSX builds going: https://bugzilla.mozilla.org/show_bug.cgi?id=1031085
- Gaia-ui-tests on emulator
- Kim Moir working on creating a new buildbot platform for faster emulators in https://bugzilla.mozilla.org/show_bug.cgi?id=1034055 ; we'll use this once it's ready
Gecko
Gaia
- Gaia-try priority:
- reduce priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1035304
- Can we live with priority 4 for now -- moving to 5 would be a killer for gaia devs if we really start seeing wait times anything close to 8 hours
- multiple repos: https://bugzilla.mozilla.org/show_bug.cgi?id=1037005
- this approach seems very reasonable, though jhford & aki say it's a complex implementation
- reduce priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1035304
Security [Paul]
- seccomp
Stability [Naoki]
no longer reporting here.
Other
New Performance Metrics in-progress
- 2.0
- 2.1
- Working on these blocking issues before transitioning to these new metrics from cold_load_time: