New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 598412 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Apr 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug



Sign in to add a comment

V4UpdateProtocolManagerTests flaking on Android

Project Member Reported by dfalcant...@chromium.org, Mar 28 2016

Issue description

These have been flaky since they were added, and for the same cause:

V4UpdateProtocolManagerTest.TestGetUpdatesErrorHandlingResponseCode crash:
https://build.chromium.org/p/chromium.android/builders/Lollipop%20Tablet%20Tester/builds/2430/

C  106.547s Main  ********************************************************************************
C  106.547s Main  Detailed Logs
C  106.547s Main  ********************************************************************************
C  106.550s Main  [CRASH] V4UpdateProtocolManagerTest.TestGetUpdatesErrorHandlingResponseCode:
C  106.550s Main  [ RUN      ] V4UpdateProtocolManagerTest.TestGetUpdatesErrorHandlingResponseCode
C  106.550s Main  [FATAL:v4_update_protocol_manager_unittest.cc(161)] Check failed: fetcher. 
C  106.551s Main  #00 0xa0703bfd /data/app/org.chromium.native_test-1/lib/arm/lib_components_unittests__library.so+0x03054bfd
C  106.551s Main  #01 0x9e19fffb /data/app/org.chromium.native_test-1/lib/arm/lib_components_unittests__library.so+0x00af0ffb
C  106.551s Main  #02 0xa076120f /data/app/org.chromium.native_test-1/lib/arm/lib_components_unittests__library.so+0x030b220f
C  106.551s Main  #03 0xa0761341 /data/app/org.chromium.native_test-1/lib/arm/lib_components_unittests__library.so+0x030b2341
C  106.551s Main  #04 0xa07613c9 /data/app/org.chromium.native_test-1/lib/arm/lib_components_unittests__library.so+0x030b23c9
C  106.551s Main  #05 0xa0763c05 /data/app/org.chromium.native_test-1/lib/arm/lib_components_unittests__library.so+0x030b4c05
C  106.551s Main  #06 0xa075d817 /data/app/org.chromium.native_test-1/lib/arm/lib_components_unittests__library.so+0x030ae817
C  106.551s Main  #07 0x9db0a2d3 /data/app/org.chromium.native_test-1/lib/arm/lib_components_unittests__library.so+0x0045b2d3
C  106.551s Main  #08 0x9db15c47 /data/app/org.chromium.native_test-1/lib/arm/lib_components_unittests__library.so+0x00466c47
C  106.551s Main  #09 0x9da71187 /data/app/org.chromium.native_test-1/lib/arm/lib_components_unittests__library.so+0x003c2187
C  106.551s Main  #10 0xa06e895f /data/app/org.chromium.native_test-1/lib/arm/lib_components_unittests__library.so+0x0303995f
C  106.551s Main  #11 0xa38ab62f /data/dalvik-cache/arm/data@app@org.chromium.native_test-1@base.apk@classes.dex+0x007a662f
C  106.551s Main  
C  106.551s Main  [ERROR:test_suite.cc(258)] Currently running: V4UpdateProtocolManagerTest.TestGetUpdatesErrorHandlingResponseCode
C  106.551s Main  ********************************************************************************



V4UpdateProtocolManagerTest.TestGetUpdatesErrorHandlingNetwork crash:
https://build.chromium.org/p/chromium.android/builders/Lollipop%20Tablet%20Tester/builds/2427/

C  106.327s Main  ********************************************************************************
C  106.327s Main  Detailed Logs
C  106.327s Main  ********************************************************************************
C  106.331s Main  [CRASH] V4UpdateProtocolManagerTest.TestGetUpdatesErrorHandlingNetwork:
C  106.331s Main  [ RUN      ] V4UpdateProtocolManagerTest.TestGetUpdatesErrorHandlingNetwork
C  106.331s Main  [FATAL:v4_update_protocol_manager_unittest.cc(138)] Check failed: fetcher. 
C  106.331s Main  #00 0xa06cca5d /data/app/org.chromium.native_test-1/lib/arm/lib_components_unittests__library.so+0x03053a5d
C  106.331s Main  #01 0x9e16951d /data/app/org.chromium.native_test-1/lib/arm/lib_components_unittests__library.so+0x00af051d
C  106.331s Main  #02 0xa072a06f /data/app/org.chromium.native_test-1/lib/arm/lib_components_unittests__library.so+0x030b106f
C  106.331s Main  #03 0xa072a1a1 /data/app/org.chromium.native_test-1/lib/arm/lib_components_unittests__library.so+0x030b11a1
C  106.331s Main  #04 0xa072a229 /data/app/org.chromium.native_test-1/lib/arm/lib_components_unittests__library.so+0x030b1229
C  106.331s Main  #05 0xa072ca65 /data/app/org.chromium.native_test-1/lib/arm/lib_components_unittests__library.so+0x030b3a65
C  106.331s Main  #06 0xa0726677 /data/app/org.chromium.native_test-1/lib/arm/lib_components_unittests__library.so+0x030ad677
C  106.331s Main  #07 0x9dad410b /data/app/org.chromium.native_test-1/lib/arm/lib_components_unittests__library.so+0x0045b10b
C  106.331s Main  #08 0x9dadfa7f /data/app/org.chromium.native_test-1/lib/arm/lib_components_unittests__library.so+0x00466a7f
C  106.331s Main  #09 0x9da3b007 /data/app/org.chromium.native_test-1/lib/arm/lib_components_unittests__library.so+0x003c2007
C  106.331s Main  #10 0xa06b17bf /data/app/org.chromium.native_test-1/lib/arm/lib_components_unittests__library.so+0x030387bf
C  106.331s Main  #11 0xa387462f /data/dalvik-cache/arm/data@app@org.chromium.native_test-1@base.apk@classes.dex+0x007a662f
C  106.331s Main  
C  106.331s Main  [ERROR:test_suite.cc(258)] Currently running: V4UpdateProtocolManagerTest.TestGetUpdatesErrorHandlingNetwork
C  106.331s Main  ********************************************************************************


KitKat tester:
https://build.chromium.org/p/chromium.android/builders/KitKat%20Tablet%20Tester/builds/3564

I  107.184s run_tests_on_device(05837e65)  Note: Google Test filter = V4UpdateProtocolManagerTest.TestGetUpdatesErrorHandlingResponseCode
I  107.184s run_tests_on_device(05837e65)  [==========] Running 1 test from 1 test case.
I  107.184s run_tests_on_device(05837e65)  [----------] Global test environment set-up.
I  107.184s run_tests_on_device(05837e65)  [----------] 1 test from V4UpdateProtocolManagerTest
I  107.184s run_tests_on_device(05837e65)  [ RUN      ] V4UpdateProtocolManagerTest.TestGetUpdatesErrorHandlingResponseCode
I  107.184s run_tests_on_device(05837e65)  [FATAL:v4_update_protocol_manager_unittest.cc(161)] Check failed: fetcher. 
I  107.184s run_tests_on_device(05837e65)  #00 0x7873dbfd /data/app-lib/org.chromium.native_test-1/lib_components_unittests__library.so+0x03054bfd
I  107.184s run_tests_on_device(05837e65)  #01 0x761d9ffb /data/app-lib/org.chromium.native_test-1/lib_components_unittests__library.so+0x00af0ffb
I  107.184s run_tests_on_device(05837e65)  #02 0x7879b20f /data/app-lib/org.chromium.native_test-1/lib_components_unittests__library.so+0x030b220f
I  107.184s run_tests_on_device(05837e65)  #03 0x7879b341 /data/app-lib/org.chromium.native_test-1/lib_components_unittests__library.so+0x030b2341
I  107.184s run_tests_on_device(05837e65)  #04 0x7879b3c9 /data/app-lib/org.chromium.native_test-1/lib_components_unittests__library.so+0x030b23c9
I  107.184s run_tests_on_device(05837e65)  #05 0x7879dc05 /data/app-lib/org.chromium.native_test-1/lib_components_unittests__library.so+0x030b4c05
I  107.184s run_tests_on_device(05837e65)  #06 0x78797817 /data/app-lib/org.chromium.native_test-1/lib_components_unittests__library.so+0x030ae817
I  107.184s run_tests_on_device(05837e65)  #07 0x75b442d3 /data/app-lib/org.chromium.native_test-1/lib_components_unittests__library.so+0x0045b2d3
I  107.184s run_tests_on_device(05837e65)  #08 0x75b4fc47 /data/app-lib/org.chromium.native_test-1/lib_components_unittests__library.so+0x00466c47
I  107.184s run_tests_on_device(05837e65)  #09 0x75aab187 /data/app-lib/org.chromium.native_test-1/lib_components_unittests__library.so+0x003c2187
I  107.184s run_tests_on_device(05837e65)  #10 0x7872295f /data/app-lib/org.chromium.native_test-1/lib_components_unittests__library.so+0x0303995f
I  107.184s run_tests_on_device(05837e65)  #11 0x4151cbcf /system/lib/libdvm.so+0x0001dbcf
I  107.184s run_tests_on_device(05837e65)  #12 0x4154d125 /system/lib/libdvm.so+0x0004e125
I  107.184s run_tests_on_device(05837e65)  #13 0x41525fe3 /system/lib/libdvm.so+0x00026fe3
I  107.184s run_tests_on_device(05837e65)  #14 0x4152cfa3 /system/lib/libdvm.so+0x0002dfa3
I  107.184s run_tests_on_device(05837e65)  #15 0x4152a63b /system/lib/libdvm.so+0x0002b63b
I  107.185s run_tests_on_device(05837e65)  #16 0x4155f863 /system/lib/libdvm.so+0x00060863
I  107.185s run_tests_on_device(05837e65)  #17 0x415677c5 /system/lib/libdvm.so+0x000687c5
I  107.185s run_tests_on_device(05837e65)  #18 0x41525fe3 /system/lib/libdvm.so+0x00026fe3
I  107.185s run_tests_on_device(05837e65)  #19 0x4152cfa3 /system/lib/libdvm.so+0x0002dfa3
I  107.185s run_tests_on_device(05837e65)  #20 0x4152a63b /system/lib/libdvm.so+0x0002b63b
I  107.185s run_tests_on_device(05837e65)  #21 0x4155f57f /system/lib/libdvm.so+0x0006057f
I  107.185s run_tests_on_device(05837e65)  #22 0x41548d0d /system/lib/libdvm.so+0x00049d0d
I  107.185s run_tests_on_device(05837e65)  #23 0x401c12b3 /system/lib/libandroid_runtime.so+0x0004d2b3
I  107.185s run_tests_on_device(05837e65)  #24 0x401c1fd9 /system/lib/libandroid_runtime.so+0x0004dfd9
I  107.185s run_tests_on_device(05837e65)  #25 0x4008405d /system/bin/app_process+0x0000105d
I  107.185s run_tests_on_device(05837e65)  #26 0x400bb34b /system/lib/libc.so+0x0000e34b
I  107.185s run_tests_on_device(05837e65)  #27 0x40083d7f /system/bin/app_process+0x00000d7f
I  107.185s run_tests_on_device(05837e65)  
I  107.185s run_tests_on_device(05837e65)  [ERROR:test_suite.cc(258)] Currently running: V4UpdateProtocolManagerTest.TestGetUpdatesErrorHandlingResponseCode
I  107.185s run_tests_on_device(05837e65)  
I  107.185s run_tests_on_device(05837e65)  FAILURES!!! Tests run: 1, Failures: 0, Errors: 1
I  107.185s run_tests_on_device(05837e65)  Finished running tests on this device.
I  107.185s run_tests_on_device(05984fda)  Finished running tests on this device.
I  107.186s run_tests_on_device(04996ae8)  Finished running tests on this device.
I  107.186s run_tests_on_device(057ccb85)  Finished running tests on this device.
I  107.186s run_tests_on_device(0597cb68)  Finished running tests on this device.
I  107.186s run_tests_on_device(0a587045)  Finished running tests on this device.
I  107.186s run_tests_on_device(0599f782)  Finished running tests on this device.
I  107.191s Main  FINISHED TRY #3/3
I  107.191s Main  1 failed tests remain.
C  107.202s Main  ********************************************************************************
 
Summary: V4UpdateProtocolManagerTests flaking on Android (was: V4UpdateProtocolManagerTest.TestGetUpdatesErrorHandlingResponseCode and V4UpdateProtocolManagerTest.TestGetUpdatesErrorHandlingNetwork flakily failing on KK and L bots)
Actually all the other tests seem to flakily fail when I run locally, as well:

  I   47.170s run_tests_on_device(059fb2dc)  [ RUN      ] V4UpdateProtocolManagerTest.TestGetUpdatesNoError
  I   47.170s run_tests_on_device(059fb2dc)  [ERROR:memory_mapped_file.cc(40)] Couldn't open /storage/emulated/0/paks/content_shell.pak
  I   47.170s run_tests_on_device(059fb2dc)  [ERROR:data_pack.cc(80)] Failed to mmap datapack
 I   47.170s run_tests_on_device(059fb2dc)  [FATAL:v4_update_protocol_manager_unittest.cc(202)] Check failed: fetcher. 
  I   47.170s run_tests_on_device(059fb2dc)  #00 0xa0fc1667 /data/app/org.chromium.native_test-2/lib/arm/lib_components_unittests__library.so+0x03513667
  I   47.170s run_tests_on_device(059fb2dc)  #01 0x9e66dca3 /data/app/org.chromium.native_test-2/lib/arm/lib_components_unittests__library.so+0x00bbfca3
  I   47.170s run_tests_on_device(059fb2dc)  #02 0xa1021267 /data/app/org.chromium.native_test-2/lib/arm/lib_components_unittests__library.so+0x03573267
  I   47.171s run_tests_on_device(059fb2dc)  #03 0xa10218cd /data/app/org.chromium.native_test-2/lib/arm/lib_components_unittests__library.so+0x035738cd
  I   47.171s run_tests_on_device(059fb2dc)  #04 0xa1021be1 /data/app/org.chromium.native_test-2/lib/arm/lib_components_unittests__library.so+0x03573be1
  I   47.171s run_tests_on_device(059fb2dc)  #05 0xa10252db /data/app/org.chromium.native_test-2/lib/arm/lib_components_unittests__library.so+0x035772db
  I   47.171s run_tests_on_device(059fb2dc)  #06 0xa1025075 /data/app/org.chromium.native_test-2/lib/arm/lib_components_unittests__library.so+0x03577075
  I   47.171s run_tests_on_device(059fb2dc)  #07 0x9ded2ae3 /data/app/org.chromium.native_test-2/lib/arm/lib_components_unittests__library.so+0x00424ae3
  I   47.171s run_tests_on_device(059fb2dc)  #08 0x9dede971 /data/app/org.chromium.native_test-2/lib/arm/lib_components_unittests__library.so+0x00430971
  I   47.171s run_tests_on_device(059fb2dc)  #09 0x9dec5e59 /data/app/org.chromium.native_test-2/lib/arm/lib_components_unittests__library.so+0x00417e59
  I   47.171s run_tests_on_device(059fb2dc)  #10 0xa0fa86e7 /data/app/org.chromium.native_test-2/lib/arm/lib_components_unittests__library.so+0x034fa6e7
  I   47.171s run_tests_on_device(059fb2dc)  #11 0xa38313b7 /data/dalvik-cache/arm/data@app@org.chromium.native_test-2@base.apk@classes.dex+0x008d53b7
  I   47.172s run_tests_on_device(059fb2dc)  
  I   47.172s run_tests_on_device(059fb2dc)  [ERROR:test_suite.cc(258)] Currently running: V4UpdateProtocolManagerTest.TestGetUpdatesNoError
  I   47.172s run_tests_on_device(059fb2dc)  
  I   47.172s run_tests_on_device(059fb2dc)  FAILURES!!! Tests run: 1, Failures: 0, Errors: 1
  I   47.172s run_tests_on_device(059fb2dc)  Finished running tests on this device.

Broadening the bug and disabling all three on Android.
Project Member

Comment 2 by bugdroid1@chromium.org, Mar 28 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/b77c54468f4c29a08e237e4f104d2cab1bf93732

commit b77c54468f4c29a08e237e4f104d2cab1bf93732
Author: dfalcantara <dfalcantara@chromium.org>
Date: Mon Mar 28 22:33:00 2016

Disable V4UpdateProtocolManagerTests on Android

They fail flakily on Android.  Seems to be a timing issue with the fetcher;
see bug for details.

BUG= 598412 

Review URL: https://codereview.chromium.org/1835833003

Cr-Commit-Position: refs/heads/master@{#383583}

[modify] https://crrev.com/b77c54468f4c29a08e237e4f104d2cab1bf93732/components/safe_browsing_db/v4_update_protocol_manager_unittest.cc

Comment 3 by vakh@chromium.org, Mar 29 2016

Cc: dfalcant...@chromium.org
Is this happening on a particular device or emulator? I tried running these tests on two different phones (one Nexus 6, one AndroidOne) and the tests pass on both of them.

Here's the command I am running:
./out/Default/bin/run_components_unittests -v -f *V4UpdateProtocolManager*

Here's the output:
I   37.103s run_tests_on_device(ZX1G22K9C4)  >>ScopedMainEntryLogger
I   37.103s run_tests_on_device(ZX1G22K9C4)  Note: Google Test filter = V4UpdateProtocolManagerTest.TestGetUpdatesErrorHandlingNetwork:V4UpdateProtocolManagerTest.TestGetUpdatesErrorHandlingResponseCode:V4UpdateProtocolManagerTest.TestGetUpdatesNoError
I   37.103s run_tests_on_device(ZX1G22K9C4)  [==========] Running 3 tests from 1 test case.
I   37.103s run_tests_on_device(ZX1G22K9C4)  [----------] Global test environment set-up.
I   37.103s run_tests_on_device(ZX1G22K9C4)  [----------] 3 tests from V4UpdateProtocolManagerTest
I   37.103s run_tests_on_device(ZX1G22K9C4)  [ RUN      ] V4UpdateProtocolManagerTest.TestGetUpdatesErrorHandlingNetwork
I   37.104s run_tests_on_device(ZX1G22K9C4)  [       OK ] V4UpdateProtocolManagerTest.TestGetUpdatesErrorHandlingNetwork (0 ms)
I   37.104s run_tests_on_device(ZX1G22K9C4)  [ RUN      ] V4UpdateProtocolManagerTest.TestGetUpdatesErrorHandlingResponseCode
I   37.104s run_tests_on_device(ZX1G22K9C4)  [       OK ] V4UpdateProtocolManagerTest.TestGetUpdatesErrorHandlingResponseCode (0 ms)
I   37.104s run_tests_on_device(ZX1G22K9C4)  [ RUN      ] V4UpdateProtocolManagerTest.TestGetUpdatesNoError
I   37.104s run_tests_on_device(ZX1G22K9C4)  [       OK ] V4UpdateProtocolManagerTest.TestGetUpdatesNoError (1 ms)
I   37.104s run_tests_on_device(ZX1G22K9C4)  [----------] 3 tests from V4UpdateProtocolManagerTest (21 ms total)
I   37.104s run_tests_on_device(ZX1G22K9C4)
I   37.104s run_tests_on_device(ZX1G22K9C4)  [----------] Global test environment tear-down
I   37.104s run_tests_on_device(ZX1G22K9C4)  [==========] 3 tests from 1 test case ran. (22 ms total)
I   37.104s run_tests_on_device(ZX1G22K9C4)  [  PASSED  ] 3 tests.
I   37.104s run_tests_on_device(ZX1G22K9C4)
I   37.105s run_tests_on_device(ZX1G22K9C4)  OK (3 tests)
I   37.105s run_tests_on_device(ZX1G22K9C4)  Finished running tests on this device.

Comment 4 by vakh@chromium.org, Mar 29 2016

Components: Services>Safebrowsing
The failures above were Tablet testers, so the Nexus 6 wouldn't count.

Comment 6 by vakh@chromium.org, Mar 30 2016

Status: Started (was: Assigned)

Comment 8 by vakh@chromium.org, Apr 1 2016

Status: Fixed (was: Started)

Sign in to add a comment