The wiki is being retired!
Documentation is now handled by the same processes we use for code: Add something to the Documentation/ directory in the coreboot repo, and it will be rendered to https://doc.coreboot.org/. Contributions welcome!
Raptor Engineering hosts an automated test system which checks the boards listed below for proper functionality every six hours. Successful test results are recorded to the board status repository, while failed tests are reported to the coreboot mailing list.
Where possible, an extended test sequence is utilized. This sequence checks CBMEM, dmimdecode, and nvramtool for proper functionality and fails verification if any errors are generated by the listed tools. As the current coreboot qemu boards do not support NVRAM, on qemu boards a basic test sequence is utilized which only verifies bootability.
Automated tests for patchsets on Gerrit are available by adding the "Raptor Engineering Automated Test Stand <email@example.com>" user as a reviewer. If any board fails verification the test stand will set Verified-1, otherwise if all boards pass verification it will set Verified+1.
All tests are run in parallel. Coreboot serial output is disabled by default so that correct timestamps are uploaded, but if a board fails to boot the test stand will automatically retry with full serial debugging enabled. As a result of this fallback mechanism, successful tests will take around 10 minutes while failed tests will take at least half an hour.
|Board||ASUS KFSN4-DRE||QEMU x86 q35/ich9|
|CPU||2x Opteron 8347 (Fam10h @ 1.9GHz / 4 cores ea.)||1x emulated x86_64|
|RAM||2GB DDR2-667 on Node 0 channel 0
2GB DDR2-667 on Node 0 channel 1
1GB DDR2-667 on Node 1 channel 0
|1GB emulated DDR|
|OS||Debian Jessie 64-bit, kernel 3.16.0||Debian Jessie 64-bit, kernel 3.16.0|
|Networking||2x Broadcom NetXtreme BCM5721||1x Intel E1000 82540EM|
|Successful Test||Failed Boot||Failed Build|
|cbmem timestamps||RS232 serial log||Build log|
|cbmem console log|
|RS232 serial log|