Skip to content
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

Closed
foolip opened this issue Apr 17, 2018 · 11 comments
Closed
Assignees

Comments

@foolip
Copy link
Member

foolip commented Apr 17, 2018

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.

@foolip
Copy link
Member Author

foolip commented Apr 17, 2018

Issues for getting experimental results:

@jugglinmike
Copy link
Contributor

Results for experimental builds of Chrome and Firefox are now available in the same format/location as the results for stable builds.

@foolip
Copy link
Member Author

foolip commented Apr 17, 2018

@jugglinmike, are the unsplit wptreport JSON files also preserved somewhere?

@jugglinmike
Copy link
Contributor

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.

@foolip
Copy link
Member Author

foolip commented Apr 17, 2018

Nah, if you don't happen to have it then let's treat it like all other results and transition by re-merging them.

@lukebjerring
Copy link
Contributor

I'm going to do this in a few steps.
First up, I'll add ?label=unstable but spoof it under the hood to change the browser names to [name]-experimental during the query, and we'll set that sit in staging until results-receiver progresses.

@foolip
Copy link
Member Author

foolip commented Jul 23, 2018

@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?

@Hexcles
Copy link
Member

Hexcles commented Jul 25, 2018

This falls under the umbrella issue I just filed #379 . Perhaps we should create a project.

@foolip
Copy link
Member Author

foolip commented Aug 17, 2018

@TimothyGu has been using wpt.fyi for his work on HTML document.open() interop, and told me that finding this label was difficult. So bump :)

@lukebjerring
Copy link
Contributor

Closing this as a dupe of #379, which will be fixed via #535

@foolip
Copy link
Member Author

foolip commented Oct 4, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants