-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose results for experimental browsers in a way that is easily linked #60
Comments
Issues for getting experimental results: |
Results for experimental builds of Chrome and Firefox are now available in the same format/location as the results for stable builds. |
@jugglinmike, are the unsplit wptreport JSON files also preserved somewhere? |
Nope. We can start doing this if you like, but storing the complete WPT report is part of @Hexcles' proposal for the results receiver. Unless there is some specific value in the unsplit files themselves (and depending on how much time Robert will need), it might be wise to wait for the new results receiver. |
Nah, if you don't happen to have it then let's treat it like all other results and transition by re-merging them. |
I'm going to do this in a few steps. |
@Orphis asked me about experimental runs on wpt.fyi today and I pointed him at https://wpt.fyi/results/?label=experimental. @lukebjerring, is all that remains of this issue to make experimental runs more discoverable? |
This falls under the umbrella issue I just filed #379 . Perhaps we should create a project. |
@TimothyGu has been using wpt.fyi for his work on HTML |
There is something left beyond #535, which is to make it easy to discover that ?label=experimental is a useful view, which isn't quite the same as the ability to pick an arbitrary set of runs. |
This is the frontend part of web-platform-tests/results-collection#146.
@lukebjerring has suggested we could use a label system to be able to mix-and-match. Anything that will allow us to have one link for Chrome+Edge+Firefox+Safari stable, and another for their most recent pre-stable builds, would do the job.
The text was updated successfully, but these errors were encountered: