1 comment:

File Documentation/technotes/2019-12-firmware-testing.md:
- Patch Set #7, Line 6:
```
both Chrome OS test
runners assume that the DUT (Device Under Test) has an operational
kernel + network + sshd
```
  The tast design principles (https://chromium.googlesource. […]
  It's not just moving the connection somewhere else. The test system also (for the most part) assumes that the interaction over that connection is "run a program on the DUT" which we also don't do.
  I guess we could get rid of that as well, but at what point are we just stuffing two completely different systems into a single binary?

To view, visit change 37643. To unsubscribe, or for help writing mail filters, visit settings.