Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 1 user
Status: Duplicate
Merged: issue 715011
Owner: ----
Closed: Aug 16
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment
poppy-release: chromeos-ec UnitTests failure
Project Member Reported by tfiga@chromium.org, Aug 16 Back to list
Build: https://luci-milo.appspot.com/buildbot/chromeos/poppy-release/657
Logs: https://uberchromegw.corp.google.com/i/chromeos/builders/poppy-release/builds/657/steps/UnitTest/logs/stdio

Failures:

chromeos-ec-0.0.1-r4098: Test nvmem timed out after 10 seconds!
chromeos-ec-0.0.1-r4098: 
chromeos-ec-0.0.1-r4098: ====== Emulator output ======
chromeos-ec-0.0.1-r4098: No flash storage found. Initializing to 0xff.
chromeos-ec-0.0.1-r4098: No RAM data found. Initializing to 0x00.
chromeos-ec-0.0.1-r4098: Console input initialized
chromeos-ec-0.0.1-r4098: 
chromeos-ec-0.0.1-r4098: 
chromeos-ec-0.0.1-r4098: 
chromeos-ec-0.0.1-r4098: 
chromeos-ec-0.0.1-r4098: --- Emulator initialized after reboot ---
chromeos-ec-0.0.1-r4098: 
chromeos-ec-0.0.1-r4098: [Reset cause: power-on]
chromeos-ec-0.0.1-r4098: 
chromeos-ec-0.0.1-r4098: [0.000327 SW 0x04]
chromeos-ec-0.0.1-r4098: 
chromeos-ec-0.0.1-r4098: Running test_corrupt_nvmem...nvmem_find_partition:300 partiton 0 verification FAILED
chromeos-ec-0.0.1-r4098: 
chromeos-ec-0.0.1-r4098: nvmem_find_partition:300 partiton 1 verification FAILED
chromeos-ec-0.0.1-r4098: 
chromeos-ec-0.0.1-r4098: [0.004470 nvmem_find_partition: No Valid Partition found, will reinitialize!]
chromeos-ec-0.0.1-r4098: 
chromeos-ec-0.0.1-r4098: [0.049294 Active Nvmem partition set to 1]
chromeos-ec-0.0.1-r4098: 
chromeos-ec-0.0.1-r4098: OK
chromeos-ec-0.0.1-r4098: 
chromeos-ec-0.0.1-r4098: Running test_fully_erased_nvmem...nvmem_find_partition:300 partiton 0 verification FAILED
chromeos-ec-0.0.1-r4098: 
chromeos-ec-0.0.1-r4098: nvmem_find_partition:300 partiton 1 verification FAILED
chromeos-ec-0.0.1-r4098: 
chromeos-ec-0.0.1-r4098: [0.095999 nvmem_find_partition: No Valid Partition found, will reinitialize!]
chromeos-ec-0.0.1-r4098: 
chromeos-ec-0.0.1-r4098: [0.138801 Active Nvmem partition set to 1]
chromeos-ec-0.0.1-r4098: 
chromeos-ec-0.0.1-r4098: OK
chromeos-ec-0.0.1-r4098: 
chromeos-ec-0.0.1-r4098: Running test_configured_nvmem...[0.138821 Active Nvmem partition set to 1]
chromeos-ec-0.0.1-r4098: 
chromeos-ec-0.0.1-r4098: OK
chromeos-ec-0.0.1-r4098: 
chromeos-ec-0.0.1-r4098: Running test_write_read_sequence...OK
chromeos-ec-0.0.1-r4098: 
chromeos-ec-0.0.1-r4098: Running test_write_full_multi...Stack trace of task 6 (<< test runner >>):
chromeos-ec-0.0.1-r4098: #0  /build/poppy/lib64/libc.so.6(__open64+0x2d) [0x7f96a2a05c3d]
chromeos-ec-0.0.1-r4098:     ??:0
chromeos-ec-0.0.1-r4098: #1  /build/poppy/lib64/libc.so.6(_IO_file_open+0x8e) [0x7f96a299491e]
chromeos-ec-0.0.1-r4098:     ??:0
chromeos-ec-0.0.1-r4098: #2  /build/poppy/lib64/libc.so.6(_IO_file_fopen+0xf0) [0x7f96a2994a80]
chromeos-ec-0.0.1-r4098:     ??:0
chromeos-ec-0.0.1-r4098: #3  /build/poppy/lib64/libc.so.6(+0x6b1c6) [0x7f96a29881c6]
chromeos-ec-0.0.1-r4098:     ??:0
chromeos-ec-0.0.1-r4098: #4  /build/poppy/usr/lib64/libsandbox.so(fopen+0xb0) [0x7f96a3601b50]
chromeos-ec-0.0.1-r4098:     ??:0
chromeos-ec-0.0.1-r4098: 
chromeos-ec-0.0.1-r4098: =============================

Looking at the change log since last working build, there doesn't seem to be anything interesting though:
https://crosland.corp.google.com/log/9844.0.0..9845.0.0

Please take a look.

 
Mergedinto: 715011
Status: Duplicate
Looks the same as 715011 . Thanks.
Sign in to add a comment