Link to build or pfq page.
https://uberchromegw.corp.google.com/i/chromeos/builders/auron-paladin/builds/10704
https://uberchromegw.corp.google.com/i/chromeos/builders/link-paladin/builds/28585


Snippet of log that contains the failure.
chromeos-ec-0.0.1-r3900: 
chromeos-ec-0.0.1-r3900: --- Emulator initialized after reboot ---
chromeos-ec-0.0.1-r3900: 
chromeos-ec-0.0.1-r3900: [Reset cause: power-on]
chromeos-ec-0.0.1-r3900: 
chromeos-ec-0.0.1-r3900: [0.000026 SW 0x04]
chromeos-ec-0.0.1-r3900: 
chromeos-ec-0.0.1-r3900: Running test_corrupt_nvmem...nvmem_find_partition:300 partiton 0 verification FAILED
chromeos-ec-0.0.1-r3900: 
chromeos-ec-0.0.1-r3900: nvmem_find_partition:300 partiton 1 verification FAILED
chromeos-ec-0.0.1-r3900: 
chromeos-ec-0.0.1-r3900: [0.000614 nvmem_find_partition: No Valid Partition found, will reinitialize!]
chromeos-ec-0.0.1-r3900: 
chromeos-ec-0.0.1-r3900: [0.001290 Active Nvmem partition set to 1]
chromeos-ec-0.0.1-r3900: 
chromeos-ec-0.0.1-r3900: OK
chromeos-ec-0.0.1-r3900: 
chromeos-ec-0.0.1-r3900: Running test_fully_erased_nvmem...nvmem_find_partition:300 partiton 0 verification FAILED
chromeos-ec-0.0.1-r3900: 
chromeos-ec-0.0.1-r3900: nvmem_find_partition:300 partiton 1 verification FAILED
chromeos-ec-0.0.1-r3900: 
chromeos-ec-0.0.1-r3900: [0.003109 nvmem_find_partition: No Valid Partition found, will reinitialize!]
chromeos-ec-0.0.1-r3900: 
chromeos-ec-0.0.1-r3900: [0.003736 Active Nvmem partition set to 1]
chromeos-ec-0.0.1-r3900: 
chromeos-ec-0.0.1-r3900: OK
chromeos-ec-0.0.1-r3900: 
chromeos-ec-0.0.1-r3900: Running test_configured_nvmem...[0.003751 Active Nvmem partition set to 1]
chromeos-ec-0.0.1-r3900: 
chromeos-ec-0.0.1-r3900: OK
chromeos-ec-0.0.1-r3900: 
chromeos-ec-0.0.1-r3900: Running test_write_read_sequence...OK
chromeos-ec-0.0.1-r3900: 
chromeos-ec-0.0.1-r3900: Running test_write_full_multi...OK
chromeos-ec-0.0.1-r3900: 
chromeos-ec-0.0.1-r3900: Running test_write_fail...nvmem_save flash erase failed
chromeos-ec-0.0.1-r3900: 
chromeos-ec-0.0.1-r3900: OK
chromeos-ec-0.0.1-r3900: 
chromeos-ec-0.0.1-r3900: Running test_buffer_overflow...Stack trace of task 6 (<< test runner >>):
chromeos-ec-0.0.1-r3900: #0  /build/auron/lib64/libc.so.6(__open64+0x2d) [0x7f6610698d1d]
chromeos-ec-0.0.1-r3900:     ??:0
chromeos-ec-0.0.1-r3900: #1  /build/auron/lib64/libc.so.6(_IO_file_open+0x8e) [0x7f66106279fe]
chromeos-ec-0.0.1-r3900:     ??:0
chromeos-ec-0.0.1-r3900: #2  /build/auron/lib64/libc.so.6(_IO_file_fopen+0xf0) [0x7f6610627b60]
chromeos-ec-0.0.1-r3900:     ??:0
chromeos-ec-0.0.1-r3900: #3  /build/auron/lib64/libc.so.6(+0x6b2a6) [0x7f661061b2a6]
chromeos-ec-0.0.1-r3900:     ??:0
chromeos-ec-0.0.1-r3900: #4  /build/auron/usr/lib64/libsandbox.so(fopen+0xb0) [0x7f6611295740]
chromeos-ec-0.0.1-r3900:     ??:0
chromeos-ec-0.0.1-r3900: 
chromeos-ec-0.0.1-r3900: =============================
chromeos-ec-0.0.1-r3900: make[1]: *** [Makefile.rules:220: run-nvmem] Error 1
chromeos-ec-0.0.1-r3900: make[1]: Leaving directory '/build/auron/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3900/work/platform/ec'
chromeos-ec-0.0.1-r3900: make: *** [Makefile.rules:145: buildall] Error 2
chromeos-ec-0.0.1-r3900:  * ERROR: chromeos-base/chromeos-ec-0.0.1-r3900::chromiumos failed (test phase):
chromeos-ec-0.0.1-r3900:  *   emake failed
chromeos-ec-0.0.1-r3900:  * 
chromeos-ec-0.0.1-r3900:  * If you need support, post the output of `emerge --info '=chromeos-base/chromeos-ec-0.0.1-r3900::chromiumos'`,
chromeos-ec-0.0.1-r3900:  * the complete build log and the output of `emerge -pqv '=chromeos-base/chromeos-ec-0.0.1-r3900::chromiumos'`.
chromeos-ec-0.0.1-r3900:  * The complete build log is located at '/build/auron/tmp/portage/logs/chromeos-base:chromeos-ec-0.0.1-r3900:20170607-062758.log'.
chromeos-ec-0.0.1-r3900:  * For convenience, a symlink to the build log is located at '/build/auron/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3900/temp/build.log'.
chromeos-ec-0.0.1-r3900:  * The ebuild environment file is located at '/build/auron/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3900/temp/environment'.
chromeos-ec-0.0.1-r3900:  * Working directory: '/build/auron/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3900/work/platform/ec'
chromeos-ec-0.0.1-r3900:  * S: '/build/auron/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3900/work/platform/ec'
chromeos-ec-0.0.1-r3900: >>> Failed to emerge chromeos-base/chromeos-ec-0.0.1-r3900 for /build/auron/, Log file:
chromeos-ec-0.0.1-r3900: >>>  '/build/auron/tmp/portage/logs/chromeos-base:chromeos-ec-0.0.1-r3900:20170607-062758.log'
chromeos-ec-0.0.1-r3900: 
chromeos-ec-0.0.1-r3900:  * Messages for package chromeos-base/chromeos-ec-0.0.1-r3900 merged to /build/auron/:
chromeos-ec-0.0.1-r3900: 
chromeos-ec-0.0.1-r3900:  * ERROR: chromeos-base/chromeos-ec-0.0.1-r3900::chromiumos failed (test phase):
chromeos-ec-0.0.1-r3900:  *   emake failed
chromeos-ec-0.0.1-r3900:  * 
chromeos-ec-0.0.1-r3900:  * If you need support, post the output of `emerge --info '=chromeos-base/chromeos-ec-0.0.1-r3900::chromiumos'`,
chromeos-ec-0.0.1-r3900:  * the complete build log and the output of `emerge -pqv '=chromeos-base/chromeos-ec-0.0.1-r3900::chromiumos'`.
chromeos-ec-0.0.1-r3900:  * The complete build log is located at '/build/auron/tmp/portage/logs/chromeos-base:chromeos-ec-0.0.1-r3900:20170607-062758.log'.
chromeos-ec-0.0.1-r3900:  * For convenience, a symlink to the build log is located at '/build/auron/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3900/temp/build.log'.
chromeos-ec-0.0.1-r3900:  * The ebuild environment file is located at '/build/auron/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3900/temp/environment'.
chromeos-ec-0.0.1-r3900:  * Working directory: '/build/auron/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3900/work/platform/ec'
chromeos-ec-0.0.1-r3900:  * S: '/build/auron/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3900/work/platform/ec'
=== Complete: job chromeos-ec-0.0.1-r3900 (4m41.2s) ===
Failed chromeos-base/chromeos-ec-0.0.1-r3900 (in 4m41.2s), retrying later.
Pending 1/51, Building 4/4, Retrying 1, [Time 23:32:39 | Elapsed 5m17.4s | Load 57.03 51.27 29.22]
Completed chromeos-base/cros-disks-0.0.1-r1843 (in 0m22.4s)
Pending 1/51, Building 3/3, Retrying 1, [Time 23:32:49 | Elapsed 5m27.3s | Load 49.79 49.91 29.02]
Completed chromeos-base/cryptohome-0.0.1-r1810 (in 2m15.2s)
Still building autotest-0.0.2-r8268 (2m24.6s). Logs in /tmp/autotest-0.0.2-r8268-AtkiPj
Still building portage-2.2.12-r11 (4m41.2s). Logs in /tmp/portage-2.2.12-r11-e7BOek
Completed sys-apps/portage-2.2.12-r11 (in 5m8.6s)
Pending 1/51, Building 1/1, Retrying 1, [Time 23:35:02 | Elapsed 7m40.4s | Load 9.72 33.84 25.88]
Still building autotest-0.0.2-r8268 (4m52.1s). Logs in /tmp/autotest-0.0.2-r8268-AtkiPj
Pending 1/51, Building 1/1, Retrying 1, [Time 23:37:03 | Elapsed 9m40.5s | Load 2.93 23.31 23.0]
Completed chromeos-base/autotest-0.0.2-r8268 (in 6m36.3s)
Pending 1/51, Building 0/0, Retrying 1, [Time 23:37:47 | Elapsed 10m24.7s | Load 2.43 20.63 22.11]
Retrying emerge of chromeos-base/chromeos-ec-0.0.1-r3900.
Started chromeos-base/chromeos-ec-0.0.1-r3900 (logged in /tmp/chromeos-ec-0.0.1-r3900-UEXQo2)
Pending 0/51, Building 1/1, [Time 23:38:47 | Elapsed 11m24.7s | Load 16.83 21.31 22.24]
Completed chromeos-base/chromeos-ec-0.0.1-r3900 (in 1m50.5s)
Pending 0/51, [Time 23:39:37 | Elapsed 12m15.2s | Load 21.07 21.86 22.38]

WARNING: The following packages failed once or more,
but succeeded upon retry. This might indicate incorrect
dependencies.
  chromeos-base/chromeos-ec-0.0.1-r3900
@@@STEP_WARNINGS@@@

Merge complete
Done
23:39:38: INFO: RunCommand: ./build_library/test_au_zip.py -o /b/cbuild/src/build/images/auron/latest-cbuildbot in /b/cbuild/src/scripts
2017/06/06 23:39:38 - test_au_zip.py - INFO    : SUCCESS for: /b/cbuild/src/build/images/auron/latest-cbuildbot/au-generator.zip
23:39:38: INFO: Running cidb query on pid 2649, repr(query) starts with <sqlalchemy.sql.expression.Update object at 0x7fe70f73b2d0>
************************************************************
** Finished Stage UnitTest - Tue, 06 Jun 2017 23:39:38 -0700 (PDT)
************************************************************