amd64-generic-tot-asan-informational and x86-generic-tot-asan-informational UnitTest timeout |
||||
Issue descriptionThe following builders are timing out in the UnitTest stage: amd64-generic-tot-asan-informational x86-generic-tot-asan-informational Starting at: https://build.chromium.org/p/chromiumos.chromium/builders/amd64-generic-tot-asan-informational/builds/8592 https://build.chromium.org/p/chromiumos.chromium/builders/x86-generic-tot-asan-informational/builds/9902 Error message: TimeoutError: Timeout occurred- waited 5400 seconds. The timeout always occurs during update_engine_unittest, but it is not clear what if anything is actually failing.
,
Mar 15 2016
There was a real use-after-free introduced in one of those CLs when the httpfetcher is destroyed in the TransferComplete() delegate call, which apparently is a valid pattern but I don't think we use in our code (outside unittests). I'll upload a CL to fix this.
,
Mar 15 2016
deymo@ - can you point me at the actual failure? One of the things we are working on is improving the failure messaging. All I notices was the timeout.
,
Mar 15 2016
Oh, the timeout is because the test spawns another process to reply the async queries send by the code under test; but the code under test dies in ASAN due to the use-after-free and the child is never killed. The test framework used in CrOS waits for all the processes to finish, and for some reason the spawned child doesn't die when the parent does. The CL to fix the use-after-free i is: https://android-review.googlesource.com/208440 The failure was: https://paste.googleplex.com/6181562114637824
,
Mar 16 2016
CL https://chromium-review.googlesource.com/#/c/332617/ landed with the uprev+fix
,
Mar 17 2016
builder turned green after that landed. |
||||
►
Sign in to add a comment |
||||
Comment 1 by steve...@chromium.org
, Mar 15 2016