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

Issue 685413 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Missing results (logcat, test results) for instrumentation tests run on swarming

Project Member Reported by mikec...@chromium.org, Jan 25 2017

Issue description

This run of chrome_public_test_apk seems to be missing much results data.
https://uberchromegw.corp.google.com/i/tryserver.chromium.android/builders/linux_android_rel_ng/builds/220185

From the results.json file for that run of chrome_public_test_apk we have entries that look like....

      "org.chromium.chrome.browser.omaha.UpdateMenuItemHelperTest#testNoVersionKnown": [
        {
          "elapsed_time_ms": 0,
          "logcat_url": "",
          "losless_snippet": "",
          "output_snippet": "",
          "output_snippet_base64:": "",
          "status": null,
          "tombstones": ""
        },
        {
          "elapsed_time_ms": 0,
          "logcat_url": "",
          "losless_snippet": "",
          "output_snippet": "",
          "output_snippet_base64:": "",
          "status": null,
          "tombstones": ""
        },
        {
          "elapsed_time_ms": 0,
          "logcat_url": "",
          "losless_snippet": "",
          "output_snippet": "",
          "output_snippet_base64:": "",
          "status": null,
          "tombstones": ""
        }

This doesn't seem at all correct considering that we have an assertion in our test_runner that 'status' is one of a list of strings.
https://cs.chromium.org/chromium/src/build/android/pylib/base/base_test_result.py?q=package:chromium&l=54

results.json:
https://isolateserver.appspot.com/browse?namespace=default-gzip&digest=686f2da0a0fc05b46ca44b97199124550ddf9d6c



Also there is no mention of that specific test ^ anywhere in the logcat file....

logcat:
https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Ftryserver.chromium.android%2Flinux_android_rel_ng%2F220185%2F%2B%2Frecipes%2Fsteps%2Fchrome_public_test_apk__with_patch__on_Android%2F0%2Fstdout


 
It might be possible some of the tests were never run. Not sure how/why that would happen though. Investigating.
Cc: yolandyan@chromium.org
+ yolandyan@, since he was trying to help we figure out how results.json had 'status': null entries and we could not figure it out.

Comment 3 by boliu@chromium.org, Jan 26 2017

I believe the CL that triggered that bot run has an infinite loop on the UI thread

so I guess make it clear that test timed out, and somehow make it easy to debug? actually if test runner made it clear that the test didn't finish at all, that probably is good enough..
Status: Assigned (was: Untriaged)

Sign in to add a comment