android_cfi_rel_ng failures do not appear to be actionable if tests hang |
||
Issue descriptionLooking at the android_cfi_rel_ng failure at https://ci.chromium.org/buildbot/tryserver.chromium.android/android_cfi_rel_ng/1 and clicking through to the failed test, we see: [ RUN ] DevToolsManagerTest.NoUnresponsiveDialogInInspectedContents [ RUN ] DevToolsManagerTest.NoUnresponsiveDialogInInspectedContents [ERROR:resource_bundle_android.cc(50)] Failed to open pak file: assets/chrome_100_percent.pak [WARNING:resource_bundle_android.cc(122)] locale_file_path.empty() for locale [ RUN ] DevToolsManagerTest.NoUnresponsiveDialogInInspectedContents [ERROR:resource_bundle_android.cc(50)] Failed to open pak file: assets/chrome_100_percent.pak [WARNING:resource_bundle_android.cc(122)] locale_file_path.empty() for locale Clicking through to the stdio from the bot, there is a mess of runner-script output, which includes a TimeoutThread which trigger a thread-dump. Unfortunately the dumped thread is the script itself, seemingly, so that there's actually nothing in the output to hint as to what state the actual hung test threads were in.
,
Jul 11
It sounds like what you're looking for is a stack trace from the frozen test? I'm pretty sure that's not unique to that bot. All gtest binaries will provide similarly unhelpful info on android if they hang. You could also try looking at the logcats for that test (click result_details link then navigate to the failing test). Though, it's not any more helpful: https://luci-logdog.appspot.com/v/?s=chromium%2Fandroid%2Fswarming%2Flogcats%2F3ea2259a0967a711%2F%2B%2Flogcat_logcat_2844416452940332717_20180711T124046-UTC_01e15a9fca604a52
,
Jul 12
Re #2: Actually, I wasn't expecting this test to hang at all, but to fail with a missed expectation. |
||
►
Sign in to add a comment |
||
Comment 1 by w...@chromium.org
, Jul 11