FilePersistentMemoryAllocatorTest.AcceptableTest generates ERROR messages |
||
Issue descriptionVersion: a4d969159adc823fe5fbe9a995241e6325e85cb6 OS: Windows 8.1 What steps will reproduce the problem? (1) python isolateserver.py download -I https://isolateserver.appspot.com --namespace default-gzip -s 20a77572e72020c062ae50284b8b19b7c03024ba --target foo (2) cd foo (3) out/Release_x64/base_unittests --gtest_filter=FilePersistentMemoryAllocatorTest.AcceptableTest What is the expected output? no ERRORs appear What do you see instead? Several messages like this: [6872:21468:0326/232014:1394156156:ERROR:persistent_memory_allocator.cc(573)] Corruption detected in shared-memory segment Please use labels and text to provide additional information.
,
Mar 29 2016
It's supposed to do that. Corruption is intentional. Are such messages not allowed?
,
Mar 30 2016
no, nothing wrong with it but I thought my CL might have caused it so it took a while for me to revert my changes and re-run. It might be worth having a comment in the test that these are expected (I did look for it).
,
Apr 4 2016
|
||
►
Sign in to add a comment |
||
Comment 1 by wfh@chromium.org
, Mar 27 2016Status: Assigned (was: Untriaged)