component_unittests/net_unittests: This program contains tests written using Google Test. |
||||
Issue descriptionThere are a bunch of crashes in components and net unittests on devices. All failures messages are Send failed, err_code=-2 bytes=0/6 Exiting. This may indicate a network error. After the failure and crash, idevice-app-runner fails to restart Send failed, err_code=-2 bytes=0/6 Exiting. idevice-app-runner returned 1 Crashed during CreditCardTest/GetCreditCardTypeTestBatch3.GetCreditCardType/7, resuming... idevice-app-runner --udid 1580b1fff293b86ce25f9b616ab8d6d3a3a147db --start com.google.gtest.components-unittests -D GKIF_SCENARIO_FILTER=-NAME:ProfileSyncServiceTest.SignOutRevokeAccessToken|ContentSuggestionsMetricsTest.ShouldLogOnSuggestionsShown|OfflinePageHeaderTest.Parse|AutofillManagerTest.GetCreditCardSuggestions_RepeatedObfuscatedNumber|... Too many test cases to resume. 1 tests failed and will be retried. Retry #1 for CreditCardTest/GetCreditCardTypeTestBatch3.GetCreditCardType/7. idevice-app-runner --udid 1580b1fff293b86ce25f9b616ab8d6d3a3a147db --start com.google.gtest.components-unittests -D GKIF_SCENARIO_FILTER=NAME:CreditCardTest/GetCreditCardTypeTestBatch3.GetCreditCardType/7 --args --gtest-filter=CreditCardTest/GetCreditCardTypeTestBatch3.GetCreditCardType/7 This program contains tests written using Google Test. You can use the following command line flags to control its behavior: Test Selection: --gtest_list_tests List the names of all tests instead of running them. The name of TEST(Foo, Bar) is "Foo.Bar". --gtest_filter=POSTIVE_PATTERNS[-NEGATIVE_PATTERNS] Run only the tests whose name matches one of the positive patterns but none of the negative patterns. '?' matches any single character; '*' matches any substring; ':' separates two patterns. --gtest_also_run_disabled_tests Run all disabled tests too. ... Most of these tests are tests with params (TEST_P) Example of failing tests CreditCardTest/GetCreditCardTypeTestBatch3.GetCreditCardType/7 RlzLibTest.ReactivationNonOrganicNonOrganic Tests/QuicHeadersStreamTest.NoConnectionLevelFlowControl/42 Example of failing runs https://uberchromegw.corp.google.com/i/internal.bling.main/builders/iphone10-device-x64/builds/4134/steps/net_unittests%20%28iPhone%206s%20iOS%2010.0.1%29%20on%20iOS-10.0.1 https://uberchromegw.corp.google.com/i/internal.bling.main/builders/iphone10-device-x64/builds/4134/steps/components_unittests%20%28iPhone%206s%20iOS%2010.0.1%29%20on%20iOS-10.0.1 https://uberchromegw.corp.google.com/i/internal.bling.main/builders/ipad10-device-x64/builds/3835/steps/components_unittests%20%28iPad%20Air%20iOS%2010.0.1%29%20on%20iOS-10.0.1
,
Mar 28 2017
rohitrao, is there anything we can do to investigate this? Is this similar to the timeout problem we had before?
,
Mar 28 2017
Sorry, I was initiating the retries incorrectly.
,
Mar 29 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/f5bc337d0967c674ab2457131e558a003f0104c2 commit f5bc337d0967c674ab2457131e558a003f0104c2 Author: smut <smut@google.com> Date: Wed Mar 29 23:11:19 2017 Change --gtest-filter argument to --gtest_filter BUG= 705510 R=baxley@chromium.org Review-Url: https://codereview.chromium.org/2782023002 . Cr-Commit-Position: refs/heads/master@{#460568} [modify] https://crrev.com/f5bc337d0967c674ab2457131e558a003f0104c2/ios/build/bots/scripts/test_runner.py
,
Apr 13 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by baxley@chromium.org
, Mar 27 2017