New issue
Advanced search Search tips

Issue 663713 link

Starred by 0 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Allow to search for test results without specifying test type

Project Member Reported by serg...@chromium.org, Nov 9 2016

Issue description

Currently one has to specify test type (normalized step name) to be able to see test results for a given test. Some tests are running in multiple different steps and it is useful to see all steps under which a given step is running.

One would have to come up with an efficient way to present these results as trybots results run on patched code and can not be aligned with waterfall results that are aligned based on revision.

This is also useful to be able to create a single link for all results for a given test, which makes it easier to link Flakiness Dashboard from Flakiness Surface and Chromium Try Flakes pages.
 
Labels: Milestone-Launch Flakiness-Surface
Currently we pick a random step name from all possible.
Status: Available (was: Untriaged)
> One would have to come up with an efficient way to present these results as trybots results run on patched code and can not be aligned with waterfall results that are aligned based on revision.

We already have this view for some of the test types, e.g. http://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=webkit_tests&tests=http%2Ftests%2Finspector%2Fnetwork%2Fnetwork-filters.html. So looks like this is not an issue.
Labels: Pri-2
If this is really a Pri-1, find an owner and update the priority.

This is the result of a bulk edit that moved high priority available bugs to a lower priority in an attempt to be more honest with bug filers.
Cc: seanmccullough@chromium.org
CC Sean, who will be taking over flakiness effort as I'm transitioning to another team.
Project Member

Comment 6 by sheriffbot@chromium.org, Aug 13

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment