net_unittests on Android failing on chromium.android/Lollipop Tablet Tester |
|||
Issue descriptionFiled by sheriff-o-matic@appspot.gserviceaccount.com on behalf of bengr@google.com net_unittests on Android failing on chromium.android/Lollipop Tablet Tester Builders failed on: - Lollipop Tablet Tester: https://build.chromium.org/p/chromium.android/builders/Lollipop%20Tablet%20Tester
,
Dec 20 2017
Each timedout task spent 5-10 minutes symbolizing traces (which is bug 774267 ): https://chromium-swarm.appspot.com/task?id=3a885268f7fd0510 https://chromium-swarm.appspot.com/task?id=3a890a2de08b7d10 https://chromium-swarm.appspot.com/task?id=3a8967fbb1558d10 That said, I'll bump timeout/shard count on the bots.
,
Dec 20 2017
Implying we're crashing a lot... Looks like you already bumped the timeout/shard count on this bot up a few weeks ago.
,
Dec 20 2017
> Implying we're crashing a lot... Are we though? Even passing tasks spend 5+ minutes symbolizing: https://chromium-swarm.appspot.com/task?id=3a89c9217b1f7410 I'm not familiar with what triggers the stack invocation. Is it a regex on stdout/logcat? Is expected test output being printed that fools the harness into thinking there's been a crash?
,
Dec 20 2017
Ah. Not quite; a process is crashing, but the test cases intended that to happen. Nevertheless, we symbolize it. As you guessed, there's a regex on stdout: https://codesearch.chromium.org/chromium/src/build/android/pylib/gtest/gtest_test_instance.py?rcl=f6befbb67127ebcf622182df6306aa2fa2fb3003&l=191 You can see the symbolized stdout in result details, e.g., look at PriorityWriteSchedulerTest in https://storage.cloud.google.com/chromium-result-details/html/net_unittests_Lollipop%20Tablet%20Tester_11181_2017_12_20_T00_12_24-UTC
,
Dec 20 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/f1a2626b5cfdde0fb46c508245a87b46ef862ed9 commit f1a2626b5cfdde0fb46c508245a87b46ef862ed9 Author: Benjamin Pastene <bpastene@chromium.org> Date: Wed Dec 20 03:29:20 2017 chromium.android: Bump shard count of net_unittests on tablet bots. Bug: 796376 Change-Id: Ifb1b14bddfad4db4fdfcef966a760a31c6720b9e Reviewed-on: https://chromium-review.googlesource.com/835647 Reviewed-by: John Budorick <jbudorick@chromium.org> Commit-Queue: Benjamin Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/master@{#525248} [modify] https://crrev.com/f1a2626b5cfdde0fb46c508245a87b46ef862ed9/testing/buildbot/chromium.android.json [modify] https://crrev.com/f1a2626b5cfdde0fb46c508245a87b46ef862ed9/testing/buildbot/test_suite_exceptions.pyl
,
Jan 8 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/d3fca3295d1a7adff0a67c0c1296f3c766d9bd31 commit d3fca3295d1a7adff0a67c0c1296f3c766d9bd31 Author: Benjamin Pastene <bpastene@chromium.org> Date: Mon Jan 08 20:12:02 2018 android: Only symbolize gtest stack traces for non-passing tests. We're spending some time symbolizing stack traces printed for passing tests: https://chromium-swarm.appspot.com/task?id=3add082b8085aa10 This'll skip that if the test passes. Bug: 796376 Change-Id: If4680171147fd15beac19ebf96bce0c7a439f857 Reviewed-on: https://chromium-review.googlesource.com/850866 Reviewed-by: Zhiling Huang <hzl@chromium.org> Reviewed-by: John Budorick <jbudorick@chromium.org> Commit-Queue: Benjamin Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/master@{#527729} [modify] https://crrev.com/d3fca3295d1a7adff0a67c0c1296f3c766d9bd31/build/android/pylib/gtest/gtest_test_instance.py |
|||
►
Sign in to add a comment |
|||
Comment 1 by bengr@chromium.org
, Dec 19 2017Components: Internals>Network Infra>Client>Chrome
Labels: OS-Android