Ticket #7394 (closed task: invalid)

Opened 6 years ago

Last modified 5 years ago

OFW Refresh

Reported by: gregorio Owned by: rsmith
Priority: normal Milestone: 8.2.0 (was Update.2)
Component: release-contract Version:
Keywords: 8.2.0:? Cc: mstone, gregorio, richard, wmb@…, joe, Charlie
Action Needed: test in build Verified: no
Deployments affected: Blocked By:
Blocking:

Description

Steps to release:

1. Nominate a package. (Richard, Mitch)

2. Include in a release-stream build. (Michael)

3. Provide some testcases. (Richard)

4. Execute some testcases against the nominated build. (Joe)

5. ...

(NB: Please annotate this release contract with all relevant tickets and wiki pages.)

Change History

Changed 6 years ago by cscott

Q2E10 is currently in joyride. I believe Q2E11 is scheduled soon. smithbone will ensure it gets into joyride.

Changed 6 years ago by rsmith

  • owner changed from richard to rsmith

q2de11 is done and ready for testing.

http://wiki.laptop.org/go/OLPC_SW-ECO_6

Changed 6 years ago by wmb@…

Firmware test matrix:

In principle, every combination of:

a) Booting with security permanently disabled, enabled with devkey, enabled without devkey, disabled but temporarily enabled via game key.

b) Reflashing OS with 4-button salute.

c) Reflashing OS with copy-nand .

d) Reflashing firmware with secure update (fw.zip)

e) Reflashing firmware with "flash" command from ok prompt.

f) Verify that secure booting works with intact images.

g) Verify that, in secure mode, OFW refuses to proceed when presented with various forms of corrupt images:

g1) Bad (truncated or with random bytes changes) os.zip, rd.zip, fs.zip, fw.zip files

g2) Errors injected into the files contained within those .zip files

g3) devkeys with errors injected into the data

g4) Data errors or truncation of the os.img file that a fs.zip file refers to

h) Verify that suspend/resume works after booting, waking up from various events - power button, lid, keyboard, mouse, game keys.

i) Run hardware diagnostics via game key or "test-all"

j) Test the operation of the various game keys that control booting modes

k) Boot from various devices - NAND, USB, SD - preferably using different kinds of USB devices (different FLASH keys, USB hard drives, etc) and different flavors of SD card (SD, SDHC, MMC) of varying capacities.

l) Test wireless network booting and reflash

Changed 6 years ago by mstone

  • cc joe added
  • next_action changed from communicate to test in build

Changed 6 years ago by joe

  • cc Charlie added

Charlie,

FYI.

Changed 5 years ago by rsmith

  • status changed from new to closed
  • resolution set to invalid
Note: See TracTickets for help on using tickets.