Document where to find logs for failing browsers (Stable/Experimental Runs)

[stephenmcgruer]

Suggestion from @KyleJu ; it would be helpful on the documentation for 'stable runs' and 'experimental runs' to link to a page where you can actually see the results.

For TaskCluster, we could link to https://github.com/web-platform-tests/wpt/commits/epochs/daily with some instruction (not sure if there's a good TaskCluster link for a given branch). For Azure we could link to https://dev.azure.com/web-platform-tests/wpt/_build?definitionId=1&_a=summary&view=branches and explain which branch to look at (epochs/daily vs epochs/three_hourly).

[stephenmcgruer]

Talking to Kyle, it seems like we should do a better job of documenting where the runs come from and what our expectations are too. For example, looking at the wpt.fyi runs page for the 'experimental runs' section is very confusing because the browsers don't (and aren't expected to) run at the same frequency; Chrome/Firefox run much more often than the others.

[stephenmcgruer]

Another suggestion (not directly related to browser documentation) was to have a 'file an issue' link which would link to the appropriate repository, with the labels and assignee preset (which you can do via query parameters, as long as the person who clicks on it has permissions - which they should if they're on the rotation).

See https://help.github.com/en/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters