Bug 1583488 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
**STR**
1. Go to a random plotted signature ([e.g.](https://treeherder.mozilla.org/perf.html#/graphs?timerange=1209600&series=autoland,1922257,1,1&highlightAlerts=1))
2. Click on the **autoland** hyperlink from top-left *(between the test name and the platform name)*.

Expected results:
**Tests** should show a single test with the same name & from the same platform, **but**
from the other integration branch. Which is mozilla-inbound, in our case.

What we get instead:
`No related tests found.` message.
Revision 1 by
on 
**STR**
1. Go to a random plotted signature ([e.g.](https://treeherder.mozilla.org/perf.html#/graphs?timerange=1209600&series=autoland,1922257,1,1&highlightAlerts=1))
2. Click on the **autoland** hyperlink from top-left *(between the test name and the platform name)*.

Expected results:
**Tests** should show a single test with the same name & from the same platform, **but**
from the other integration branch. Which is **mozilla-inbound**, in our case.

What we get instead:
`No related tests found.` message.
Revision 2 by
on 
**STR**
1. Go to a random plotted signature ([e.g.](https://treeherder.mozilla.org/perf.html#/graphs?timerange=1209600&series=autoland,1922257,1,1&highlightAlerts=1))
2. Click on the **autoland** hyperlink from top-left *(between the test name and the platform name)*.

Expected results:
**Related tests** should show a single test with the same name & from the same platform, **but**
from the other integration branch. Which is **mozilla-inbound**, in our case.

What we get instead:
`No related tests found.` message. Also, instead of **Related tests** header, we have **Tests** header.

Back to Bug 1583488 Comment 0