https://luci-milo.appspot.com/buildbot/chromeos/kevin-paladin/2846
https://logs.chromium.org/v/?s=chromeos%2Fbb%2Fchromeos%2Fkevin-paladin%2F2846%2F%2B%2Frecipes%2Fsteps%2FUnitTest%2F0%2Fstdout

chromeos-ec-0.0.1-r4292: Test math_util timed out after 10 seconds!
chromeos-ec-0.0.1-r4292: 
chromeos-ec-0.0.1-r4292: ====== Emulator output ======
chromeos-ec-0.0.1-r4292: No flash storage found. Initializing to 0xff.
chromeos-ec-0.0.1-r4292: No RAM data found. Initializing to 0x00.
chromeos-ec-0.0.1-r4292: 
chromeos-ec-0.0.1-r4292: 
chromeos-ec-0.0.1-r4292: 
chromeos-ec-0.0.1-r4292: 
chromeos-ec-0.0.1-r4292: --- Emulator initialized after reboot ---
chromeos-ec-0.0.1-r4292: 
chromeos-ec-0.0.1-r4292: [Reset cause: power-on]
chromeos-ec-0.0.1-r4292: 
chromeos-ec-0.0.1-r4292: [0.000027 SW 0x04]
chromeos-ec-0.0.1-r4292: 
chromeos-ec-0.0.1-r4292: Running test_acos...OK
chromeos-ec-0.0.1-r4292: 
chromeos-ec-0.0.1-r4292: Running test_rotate...OK
chromeos-ec-0.0.1-r4292: 
chromeos-ec-0.0.1-r4292: PaConsole input initialized
chromeos-ec-0.0.1-r4292: ss!
chromeos-ec-0.0.1-r4292: 
chromeos-ec-0.0.1-r4292: Console is enabled; type HELP for help.
chromeos-ec-0.0.1-r4292: 
chromeos-ec-0.0.1-r4292: > [0.000206 event set 0x00002000]
chromeos-ec-0.0.1-r4292: 
chromeos-ec-0.0.1-r4292: [0.000212 hostcmd init 0x2000]
chromeos-ec-0.0.1-r4292: 
chromeos-ec-0.0.1-r4292: Stack trace of task 1 (HOOKS):
chromeos-ec-0.0.1-r4292: #0  /lib64/libpthread.so.0(+0xfd9c) [0x7f8bd77fcd9c]
chromeos-ec-0.0.1-r4292:     ??:0
chromeos-ec-0.0.1-r4292: #1  /lib64/libpthread.so.0(+0xb700) [0x7f8bd77f8700]
chromeos-ec-0.0.1-r4292:     ??:0
chromeos-ec-0.0.1-r4292: #2  /lib64/libpthread.so.0(pthread_cond_wait+0x14f) [0x7f8bd77f9faf]
chromeos-ec-0.0.1-r4292:     ??:0
chromeos-ec-0.0.1-r4292: #3  build/host/math_util/math_util.exe(task_wait_event+0x89) [0x411f23]
chromeos-ec-0.0.1-r4292:     /build/kevin/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r4292/work/platform/ec/core/host/task.c:204
chromeos-ec-0.0.1-r4292: #4  build/host/math_util/math_util.exe(hook_task+0x1f7) [0x40aa10]
chromeos-ec-0.0.1-r4292:     /build/kevin/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r4292/work/platform/ec/common/hooks.c:243
chromeos-ec-0.0.1-r4292: #5  build/host/math_util/math_util.exe(_task_start_impl+0x79) [0x4124f8]
chromeos-ec-0.0.1-r4292:     /build/kevin/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r4292/work/platform/ec/core/host/task.c:406 (discriminator 1)
chromeos-ec-0.0.1-r4292: #6  /lib64/libpthread.so.0(+0x7214) [0x7f8bd77f4214]
chromeos-ec-0.0.1-r4292:     ??:0
chromeos-ec-0.0.1-r4292: #7  /lib64/libc.so.6(clone+0x6d) [0x7f8bd753861d]
chromeos-ec-0.0.1-r4292:     ??:0
chromeos-ec-0.0.1-r4292: 

No likely suspect CLs.

unittest stage finished ~5:15, we see that the builder was heavily loaded.
https://viceroy.corp.google.com/chromeos/build_details?build_id=1983809

But unittest was tried twice, and it failed both times. It still is flaky under load, which is bad for a unittest.


 issue 715011  could be related / same prblem in another unittest.
P2, pending recurrence, at which point this should become P1. We really don't like flaky unittests ;)