New issue
Advanced search Search tips

Issue 653211 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 405799
Owner: ----
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: ----



Sign in to add a comment

Many Android bots not showing results in the flakiness dashboard

Project Member Reported by twelling...@chromium.org, Oct 5 2016

Issue description

It looks like the numerous bots on the public Android waterfalls are not uploading its results to the upstream flakiness dashboard.

The only builders that are listed for chrome_public_test_apk are:
- chromium.linux:Android Tests
- chromium.android:Android Swarm Builder
- chromium.android:Marshmallow 64 bit Tester
- chromium.android.fyi:Android Cloud Tests


I was expecting to see many more bots, e.g.
- Marshmallow Tablet Tester
- Lollipop Phone Tester
- Lollipop Low-end Tester
- KitKat Tablet Tester
- Android Tests (dbg)
etc.

It looks like these bots also aren't uploading results for other tests suites. Fore example, content_shell_test_apk only lists Android Tests, Android Swarm Builder,  Android N5X Swarm Builder, Marshmallow 64 bit Tester and Cloud Tests.
 
They certainly seem to think they're uploading, e.g. the "Upload to test-results" steps here: https://build.chromium.org/p/chromium.android/builders/Lollipop%20Phone%20Tester/builds/7153
Summary: Many Android bots not showing results in the flakiness dashboard (was: Many Android bots not uploading results to flakiness dashboard)
So maybe it's an issue with the flakiness dashboard itself?
AFAICT, yeah.

The four bots that show up are all running tests on swarming, while the ones that aren't are running tests locally. That may also be involved?
Cc: estaab@chromium.org
Status: Available (was: Untriaged)
Looks like these builders aren't being detected when scraping buildbot for builders with chrome_public_test_apk steps.

http://test-results.appspot.com/builders?callback=LOAD_BUILDBOT_DATA

I might be able to figure this out but I'm getting on a flight soon.
Mergedinto: 405799
Status: Duplicate (was: Available)
This is working now. The problem was due to  issue 405799  where the associations are derived from the first build it sees, even if that build failed early and didn't include important steps. The problem could come back but the associations are correct now.

Sign in to add a comment