The ASUS KFSN4-DRE fails verification for branch master as of commit 0f6d10ba8f8f711f2ff7fa5c8f306e18a42b8974
The following tests failed: BOOT_FAILURE
Commits since last successful test: 0f6d10b google/pyro: Update DPTF settings
See attached log for details
This message was automatically generated from Raptor Engineering's ASUS KFSN4-DRE test stand Want to test on your own equipment? Check out https://www.raptorengineering.com/content/REACTS/intro.html
Raptor Engineering also offers coreboot consulting services! Please visit https://www.raptorengineering.com for more information
Please contact Timothy Pearson at Raptor Engineering tpearson@raptorengineering.com regarding any issues stemming from this notification
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 01/23/2017 09:39 AM, Raptor Engineering Automated Coreboot Test Stand wrote:
The ASUS KFSN4-DRE fails verification for branch master as of commit 0f6d10ba8f8f711f2ff7fa5c8f306e18a42b8974
The following tests failed: BOOT_FAILURE
Commits since last successful test: 0f6d10b google/pyro: Update DPTF settings
See attached log for details
This message was automatically generated from Raptor Engineering's ASUS KFSN4-DRE test stand Want to test on your own equipment? Check out https://www.raptorengineering.com/content/REACTS/intro.html
Raptor Engineering also offers coreboot consulting services! Please visit https://www.raptorengineering.com for more information
Please contact Timothy Pearson at Raptor Engineering tpearson@raptorengineering.com regarding any issues stemming from this notification
To provide a bit of background on this, an earlier REACTS system version used on the KFSN4-DRE DUT was inadvertently testing the same coreboot revision over and over. This failure now reflects the current state of the tree on this board, however the exact point of regression is currently unknown. I will fire off some strategic tests in Gerrit to try to narrow this back down.
- -- Timothy Pearson Raptor Engineering +1 (415) 727-8645 (direct line) +1 (512) 690-0200 (switchboard) https://www.raptorengineering.com
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 01/23/2017 01:48 PM, Timothy Pearson wrote:
On 01/23/2017 09:39 AM, Raptor Engineering Automated Coreboot Test Stand wrote:
The ASUS KFSN4-DRE fails verification for branch master as of commit 0f6d10ba8f8f711f2ff7fa5c8f306e18a42b8974
The following tests failed: BOOT_FAILURE
Commits since last successful test: 0f6d10b google/pyro: Update DPTF settings
See attached log for details
This message was automatically generated from Raptor Engineering's ASUS KFSN4-DRE test stand Want to test on your own equipment? Check out https://www.raptorengineering.com/content/REACTS/intro.html
Raptor Engineering also offers coreboot consulting services! Please visit https://www.raptorengineering.com for more information
Please contact Timothy Pearson at Raptor Engineering tpearson@raptorengineering.com regarding any issues stemming from this notification
To provide a bit of background on this, an earlier REACTS system version used on the KFSN4-DRE DUT was inadvertently testing the same coreboot revision over and over. This failure now reflects the current state of the tree on this board, however the exact point of regression is currently unknown. I will fire off some strategic tests in Gerrit to try to narrow this back down.
As it turns out, a couple of obscure (custom) cbfstool calls related to fallback / normal payload swaps were the culprit here. This has been resolved for the KFSN4-DRE DUT and coreboot master is passing testing again.
Sorry for the noise!
- -- Timothy Pearson Raptor Engineering +1 (415) 727-8645 (direct line) +1 (512) 690-0200 (switchboard) https://www.raptorengineering.com
-
Raptor Engineering Automated Coreboot Test Stand -
Timothy Pearson