EngineeringProductivity/Projects/Debugging UX improvements

This project is composed of multiple projects which will be improving the overall experience when debugging issues on try.

Q4's 2016 focus is mainly improving end to end times on Try (Thunder Try project).

Context

The original discussions are discussed in here. The projects defined below are the ones we're considering tackling at this point.

P1 means that we're commiting to complete a bug within the current quarter. P2 means that it's nice to fix and we will tackle if we have time.

All possible projects - bugzilla tree dependency

Meeting

We are trying to meet every four weeks. We will be posting details in the tools mailing list. Etherpad: https://public.etherpad-mozilla.org/p/debugging_ux_improvements

Dial-in information

 # This meeting will start at 10:00-10:50AM PDT 
 # Guest:  https://v.mozilla.com/flex.html?roomdirect.html&key=43kzfyP8BDSG
 # Vidyo:  A-Team Vidyo Room
 # Phone:  650-903-0800 or 650-215-1282 x92 Conf# 98416  (US/INTL)
 #         1-800-707-2533 (pin 369) Conf# 98416 (free for anyone to join)
 # IRC:    irc://irc.mozilla.org:6697/#ateam

Project #1 - Thunder Try - Improve end to end times

Current main focus:

• Artifact builds on try
• Automation metrics
• Better sscache for try
• Hyper chunking
• Web platform tests from source checkout

Docs:

• Meeting notes - link
• Project brief - link
• Work breakdown - link
  • NOTE: Not being kept up to date
• Bug links:
  • dependency tree
  • including resolved bugs

• Possible data sources for metrics:
  • ActiveData development metrics
  • Platform Ops metrics

Tracked bugs (P1s are the ones we commit to for this quarter)

Full Query

ID	Priority	Summary	Whiteboard	Assigned to
1240644	P2	Allow skipping build and reusing existing build result for try push
1280641	P3	Implement a two-tier S3 cache for sccache	[build-run-speed-up]
1284882	P3	[tracker] Artifact builds on automation
1315030	P3	Determine how many try pushes could benefit from using artifact builds
1432287	P3	[meta] Run tests from source checkouts in CI
1294706	--	"Mochitest other" chunk on win7 debug slow and often last to complete

6 Total; 6 Open (100%); 0 Resolved (0%); 0 Verified (0%);

Maintenance

Debugging tests on interactive workers

Developers can go from requesting a Linux loaner on TaskCluster to having a debugging environment ready to run tests in a reasonable time with minimal interaction with external documentation or need a minimum amount of help.

• Meeting notes - link
• Project brief - link
• Work breakdown - link
• Bug links:
  • dependency tree
  • including resolved bugs

Tracked bugs (P1s are the ones we commit to for this quarter)

Full Query

ID	Priority	Summary	Whiteboard	Assigned to
1271677	P2	Interactive tasks should be scheduled with high priority
1284998	P2	Create tests for interactive debugging workflows
1302520	P3	Support running jittest from an interactive worker
1303031	P3	Support running Android xpcshell tests on interactive loaners
1302518	--	Support running cppunittests from an interactive worker
1302519	--	Support running gtest from an interactive worker

6 Total; 6 Open (100%); 0 Resolved (0%); 0 Verified (0%);