AutoTest/RaptorEngineering: Difference between revisions
No edit summary |
m (Use correct link) |
||
| Line 7: | Line 7: | ||
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. | 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. | ||
Test queue status is available [https://raptorengineeringinc.com/coreboot/reacts_status.php here] | Test queue status is available [https://secure.raptorengineeringinc.com/coreboot/reacts_status.php here] | ||
{| class="wikitable" | {| class="wikitable" | ||
Revision as of 22:51, 20 October 2015
Raptor Engineering hosts an automated test system which checks the boards listed below for proper functionality up to every hour. 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. Furthermore, native VGA initialization is verified by checking for correct video output. 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 <noreply@raptorengineeringinc.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.
Test queue status is available here
| 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 |
| Add-on cards | None | None |
| Peripherals | PS/2 keyboard 17" flat CRT |
None |
| Test type | Extended with video verification | Basic |
| Package | Version |
| ACPICA | 20150204 |
| binutils | 2.25 |
| gcc | 4.9.2 |
| gmp | 6.0.0a |
| libelf | 0.8.13 |
| mpc | 1.0.3 |
| mpfr | 3.1.2 |
| Successful Test | Failed Boot | Failed Build |
| cbmem timestamps | coreboot configuration | Build log |
| coreboot configuration | RS232 serial log | coreboot configuration |
| cbmem console log | ||
| dmesg output | ||
| dmidecode output | ||
| video decoding results | ||
| RS232 serial log |