https://uberchromegw.corp.google.com/i/chromeos/builders/daisy_spring-release/builds/2487/steps/UnitTest/logs/stdio

...
chromeos-ec-0.0.1-r3867: Test usb_pd passed! (0.390 seconds)
chromeos-ec-0.0.1-r3867: Test x25519 passed! (0.885 seconds)
chromeos-ec-0.0.1-r3867: Test nvmem timed out after 10 seconds!
chromeos-ec-0.0.1-r3867: 
chromeos-ec-0.0.1-r3867: ====== Emulator output ======
chromeos-ec-0.0.1-r3867: No flash storage found. Initializing to 0xff.
chromeos-ec-0.0.1-r3867: No RAM data found. Initializing to 0x00.
chromeos-ec-0.0.1-r3867: Console input initialized
chromeos-ec-0.0.1-r3867: 
chromeos-ec-0.0.1-r3867: 
chromeos-ec-0.0.1-r3867: 
chromeos-ec-0.0.1-r3867: 
chromeos-ec-0.0.1-r3867: --- Emulator initialized after reboot ---
chromeos-ec-0.0.1-r3867: 
chromeos-ec-0.0.1-r3867: [Reset cause: power-on]
chromeos-ec-0.0.1-r3867: 
chromeos-ec-0.0.1-r3867: [0.000028 SW 0x04]
chromeos-ec-0.0.1-r3867: 
chromeos-ec-0.0.1-r3867: Running test_corrupt_nvmem...nvmem_find_partition:300 partiton 0 verification FAILED
chromeos-ec-0.0.1-r3867: 
chromeos-ec-0.0.1-r3867: nvmem_find_partition:300 partiton 1 verification FAILED
chromeos-ec-0.0.1-r3867: 
chromeos-ec-0.0.1-r3867: [0.000586 nvmem_find_partition: No Valid Partition found, will reinitialize!]
chromeos-ec-0.0.1-r3867: 
chromeos-ec-0.0.1-r3867: [0.066004 Active Nvmem partition set to 1]
chromeos-ec-0.0.1-r3867: 
chromeos-ec-0.0.1-r3867: OK
chromeos-ec-0.0.1-r3867: 
chromeos-ec-0.0.1-r3867: Running test_fully_erased_nvmem...nvmem_find_partition:300 partiton 0 verification FAILED
chromeos-ec-0.0.1-r3867: 
chromeos-ec-0.0.1-r3867: nvmem_find_partition:300 partiton 1 verification FAILED
chromeos-ec-0.0.1-r3867: 
chromeos-ec-0.0.1-r3867: [0.121188 nvmem_find_partition: No Valid Partition found, will reinitialize!]
chromeos-ec-0.0.1-r3867: 
chromeos-ec-0.0.1-r3867: [0.154265 Active Nvmem partition set to 1]
chromeos-ec-0.0.1-r3867: 
chromeos-ec-0.0.1-r3867: OK
chromeos-ec-0.0.1-r3867: 
chromeos-ec-0.0.1-r3867: Running test_configured_nvmem...[0.154284 Active Nvmem partition set to 1]
chromeos-ec-0.0.1-r3867: 
chromeos-ec-0.0.1-r3867: OK
chromeos-ec-0.0.1-r3867: 
chromeos-ec-0.0.1-r3867: Running test_write_read_sequence...OK
chromeos-ec-0.0.1-r3867: 
chromeos-ec-0.0.1-r3867: Running test_write_full_multi...Stack trace of task 6 (<< test runner >>):
chromeos-ec-0.0.1-r3867: #0  /lib64/libc.so.6(__open64+0x2d) [0x7f0762792a2d]
chromeos-ec-0.0.1-r3867:     ??:0
chromeos-ec-0.0.1-r3867: #1  /lib64/libc.so.6(_IO_file_open+0x8e) [0x7f0762723dfe]
chromeos-ec-0.0.1-r3867:     ??:0
chromeos-ec-0.0.1-r3867: #2  /lib64/libc.so.6(_IO_file_fopen+0xf0) [0x7f0762723f60]
chromeos-ec-0.0.1-r3867:     ??:0
chromeos-ec-0.0.1-r3867: #3  /lib64/libc.so.6(+0x69e55) [0x7f0762717e55]
chromeos-ec-0.0.1-r3867:     ??:0
chromeos-ec-0.0.1-r3867: #4  /usr/lib64/libsandbox.so(fopen+0x9c) [0x7f0763188a9c]
chromeos-ec-0.0.1-r3867:     ??:0
chromeos-ec-0.0.1-r3867: #5  build/host/nvmem/nvmem.exe(get_persistent_storage+0x81) [0x4070c3]
chromeos-ec-0.0.1-r3867:     /build/daisy_spring/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3867/work/platform/ec/chip/host/persistence.c:38
chromeos-ec-0.0.1-r3867: #6  build/host/nvmem/nvmem.exe() [0x406806]
chromeos-ec-0.0.1-r3867:     /build/daisy_spring/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3867/work/platform/ec/chip/host/flash.c:39
chromeos-ec-0.0.1-r3867: #7  build/host/nvmem/nvmem.exe(flash_physical_erase+0x82) [0x4069fd]
chromeos-ec-0.0.1-r3867:     /build/daisy_spring/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3867/work/platform/ec/chip/host/flash.c:95
chromeos-ec-0.0.1-r3867: #8  build/host/nvmem/nvmem.exe() [0x40c723]
chromeos-ec-0.0.1-r3867:     /build/daisy_spring/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3867/work/platform/ec/common/nvmem.c:128
chromeos-ec-0.0.1-r3867: #9  build/host/nvmem/nvmem.exe(nvmem_commit+0xf5) [0x40d08e]
chromeos-ec-0.0.1-r3867:     /build/daisy_spring/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3867/work/platform/ec/common/nvmem.c:602
chromeos-ec-0.0.1-r3867: #10 build/host/nvmem/nvmem.exe() [0x412ba6]
chromeos-ec-0.0.1-r3867:     /build/daisy_spring/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3867/work/platform/ec/test/nvmem.c:134
chromeos-ec-0.0.1-r3867: #11 build/host/nvmem/nvmem.exe() [0x41328f]
chromeos-ec-0.0.1-r3867:     /build/daisy_spring/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3867/work/platform/ec/test/nvmem.c:341
chromeos-ec-0.0.1-r3867: #12 build/host/nvmem/nvmem.exe(run_test+0x184) [0x413ea1]
chromeos-ec-0.0.1-r3867:     /build/daisy_spring/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3867/work/platform/ec/test/nvmem.c:706
chromeos-ec-0.0.1-r3867: #13 build/host/nvmem/nvmem.exe(_run_test+0x11) [0x411a96]
chromeos-ec-0.0.1-r3867:     /build/daisy_spring/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3867/work/platform/ec/core/host/task.c:77
chromeos-ec-0.0.1-r3867: #14 build/host/nvmem/nvmem.exe(_task_start_impl+0x79) [0x41234a]
chromeos-ec-0.0.1-r3867:     /build/daisy_spring/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3867/work/platform/ec/core/host/task.c:406 (discriminator 1)
chromeos-ec-0.0.1-r3867: #15 /lib64/libpthread.so.0(+0x74b4) [0x7f0762a5d4b4]
chromeos-ec-0.0.1-r3867:     ??:0
chromeos-ec-0.0.1-r3867: #16 /lib64/libc.so.6(clone+0x6d) [0x7f07627a069d]
chromeos-ec-0.0.1-r3867:     ??:0
chromeos-ec-0.0.1-r3867: 
chromeos-ec-0.0.1-r3867: =============================
chromeos-ec-0.0.1-r3867: make[1]: *** [Makefile.rules:220: run-nvmem] Error 1
chromeos-ec-0.0.1-r3867: make[1]: Leaving directory '/build/daisy_spring/tmp/portage/chromeos-base/chromeos-ec-0.0.1-r3867/work/platform/ec'
chromeos-ec-0.0.1-r3867: make: *** [Makefile.rules:145: buildall] Error 2
chromeos-ec-0.0.1-r3867:  * ERROR: chromeos-base/chromeos-ec-0.0.1-r3867::chromiumos failed (test phase):
chromeos-ec-0.0.1-r3867:  *   emake failed

I'm curious why we are trying to test HW in an emulator. Is that what is really happening?
In theory this should be way _faster_ than the actual hardware (erase cycle should in "instant").