Status Update for mus+ash - 3/8/2019
Daniel Xie
Hi,
The team is working to launch Single Process Mash (SPM). Currently, SPM is on by default on ToT and on M74 branch. The plan is to have the ChromeOS test team do a full regression pass on SPM during M74 qualification. The team is also addressing launch blockers for SPM. If you see any UI related bugs, try to see if it’s affecting only SPM. In other words, if by turning off SPM (chrome://flags, "In-process window service (SingleProcessMash) disabled”), the issue does not reproduce. Please file a bug using the Proj=Mash-SingleProcess label.
Ash Refactoring
We split the ash refactoring into 2 milestones: running the mash window service in the browser process and supporting mash running in separate process. Overall, the overall headers is at 201 ash includes with tests (vs 188 last week). Excluding test includes, we are at 62 (vs 63 last week).
Mash Window Service in the Browser Process (Status: addressing launch blockers )
The team is addressing launch blockers for SPM. Currently we are at 17 bugs. There will likely be an increase in the incoming bugs as ChromeOS testing team start regressing this feature. Our team is also focusing on getting telemetry tests setup so we can address latency issues. It is anticipated that the initial bug count will increase we correctly break down bugs for tracking. Our team will continue to triage and address incoming filed issues.
Total | In Progress | Backlog | |
9/20 | 72 | 50 | 22 |
10/31 | 34 | 29 | 5 |
11/8 | 37 | 34 | 3 |
11/30 | 38 | 34 | 4 |
12/6 | 44 | 39 | 5 |
12/13 | 23 | 23 | 0 |
1/19 | 11 | 6 | 5 |
1/26 | 6 | 6 | 0 |
1/31 | 4 | 4 | 0 |
3/8 |
Mash Window Service outside of the Browser Process (Status: In progress)
As the team winds down refactoring Single Process Mash, the team will be focused on burning down blockers for running Mash in a separate process.