Projects/ARMv6 Boards

This is a page to list out the tasks for bringing up ARM v6 boards. We've decided to use the APC.io boards because they have 800Mhz CPUs with 512Mb of RAM which is the first level of ARM v6 support we would like to attain. Eventually we want to support 256 Mb of RAM but testing that in automation is likely unnecessary (and will likely be highly intermittent)

For the APC.io board we have the following tasks:

Board Readiness Pipeline A

Everything in this section is driven by the A*Team, but we may have to pull in some development folks to help debug issues, particularly with Robocop. We tend to see the most unusual issues with robocop and reftest. Once mochitest runs, it tends to be fairly stable. So I've noted the potential areas of unknowns appropriately.

• [DONE] Analyze "out of the box" image for robustness, usefulness
• [DONE] Root board
• [DONE] Run Agent, watcher, fennec

Board Specific Issues

• [ON TRACK] Understand why sdcard external storage notification doesn't fire
• [ON TRACK] Work around read-only by default sdcard partition

Mochitest

• [ON TRACK] Debug Crash on Startup with mochitest profile and Fennec
• [ON TRACK] Document other as yet unknown issues once we can run mochitest - likelihood these exist is low

Robocop

• [ON TRACK] Attempt to run once startup crash for mochitest fixed - 1 day
• [ON TRACK] Document other unknown issues once we pass that point - likelihood these exist is high

Reftest

• [ON TRACK] Attempt to run reftest once crash on startup is fixed - 1 day
• [ON TRACK] Document other unknown issues once we can run the test - likelihood these exist is moderate
• [ON TRACK] DEPENDS ON REFTEST SIZE CHANGE for low resolution - this has been an ongoing effort now for some time

Board Readiness Pipeline B

At this point, we know we are going forward with the board. So we should begin designing chassis, ordering first boards to put into the first chassis etc. Everything from this point forward should happen in parallel.

• [ON TRACK] Ateam: Run non-power cycling smoketest on APC.io Boards, fix any remaining stability issues 2-3 weeks
• [ON TRACK] Ateam: Rack APC.io boards in autophone for nightly test runs - 2 days
• [ON TRACK] Ateam: work with dev team to solve issues surrounding robocop - 2-3 weeks, parallelizable
• [ON TRACK] Ateam: work with dev team to solve issues surrounding reftest - 3-4 weeks (reftest turn around traditionally slow, parallelizable)
• [ON TRACK] IT: Design chassis for boards
• [ON TRACK] IT/Releng: Decide on initial order for boards and prototype chassis, and order them 1 day
• [ON TRACK] IT/Releng: Get pre-approval for the at scale purchase of boards and chassis - 3 days
• [ON TRACK] IT: Build one prototype chassis with boards - 2 days
• [ON TRACK] ATeam: Run smoketest with power cycling on prototype chassis - 3 days
• [ON TRACK] IT/Releng: Buy the APC.io boards & chassis at scale 1 day
• [ON TRACK] IT: Assemble full set of chassis, run board readiness scripts - 1-2 weeks
• [ON TRACK] Releng: Provision foopies and/or craft mozharness scripts and buildbot configs to deploy tests to staging - 2-3 weeks
• [ON TRACK] IT/DCops: Rack, cable, and power chassis with boards - 1 week
• [ON TRACK] Ateam/Releng/IT: Final integration stage test - fix any last issues 1-2 weeks
• [ON TRACK] Ateam: Change TBPL to recognize new board, changes to graphserver/datazilla - 3 days
• [ON TRACK] Releng: Perform reconfig to launch APC.io into production - 2 days