memory.long_running_dual_browser_test failing on internal.client.clank/integration-android-low-end-phone |
||||||||
Issue descriptionFiled by sheriff-o-matic@appspot.gserviceaccount.com on behalf of gsennton@google.com memory.long_running_dual_browser_test failing on internal.client.clank/integration-android-low-end-phone Builders failed on: - integration-android-low-end-phone: https://uberchromegw.corp.google.com/i/internal.client.clank/builders/integration-android-low-end-phone Started failing at build nr #4344: https://uberchromegw.corp.google.com/i/internal.client.clank/builders/integration-android-low-end-phone/builds/4344 The failing test is google_tip_on_100_bill
,
Feb 15 2018
,
Feb 15 2018
As of https://uberchromegw.corp.google.com/i/internal.client.clank/builders/integration-android-low-end-phone/builds/4393 the bot has been mostly green. Only three failures, each with a single failing story, and always a different one: #4394 google #4401 amazon #4408 wikipedia So no consistent failure to investigate. A single story failing out of 1200 tests run on this benchmark is an acceptable ratio for this bot.
,
Feb 20 2018
Looks like this is happening more frequently, failing every day now: https://uberchromegw.corp.google.com/i/internal.client.clank/builders/integration-android-low-end-phone Is it possible to just add some kind of retry-on-failure so this issue doesn't keep coming up on SOM?
,
Feb 21 2018
This looks like a new consistent failure. Unrelated to the previous ones. The failing story is http_en_m_wikipedia_org_wiki_Science, with the browser actually crashing: signal 11 (SIGSEGV), code 1, fault addr 0xe00cf81e in tid 4194 (Chrome_IOThread) pid: 4152, tid: 4194, name: Chrome_IOThread >>> com.google.android.apps.chrome <<< signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xe00cf81e r0 00000000 r1 a2611a88 r2 00001000 r3 b9a6d50c r4 b9a6d4d8 r5 00000000 r6 b9a6d4f4 r7 00000040 r8 a0db54b0 r9 e00cf81e sl b9a6d50c fp 00000000 ip 070cca8b sp a0db54a0 lr 988f48a7 pc 988f498c Stack Trace: RELADDR FUNCTION FILE:LINE 0077698c mojo::edk::PlatformChannelRecvmsg(mojo::edk::ScopedPlatformHandle const&, void*, unsigned int, base::circular_deque<mojo::edk::ScopedPlatformHandle>*, bool) /b/build/slave/arm-builder-rel/build/src/mojo/edk/embedder/platform_channel_utils_posix.cc:182:17 Full logs attached. I'll also kick off a bisect, hopefully will help to narrow down a culprit. From the crash message sounds like this could be related to issue 734645?
,
Feb 21 2018
,
Feb 21 2018
Actually, this is the long running test. Bisect won't work here. :-/
,
Feb 21 2018
,
Feb 21 2018
,
Feb 21 2018
,
Mar 19 2018
Has been again mostly green since: https://uberchromegw.corp.google.com/i/internal.client.clank/builders/integration-android-low-end-phone/builds/4463 If new failures occur please file a new bug. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by ctzsm@chromium.org
, Feb 14 2018