On 10/02/17 06:34, Brian Birtles wrote:
I don't expect James to file bugs for all the new failures he encounters when syncing (and I suspect if he did, many of them would end up being marked invalid/duplicate because they're features we don't implement yet), but is there somewhere we can get a report of all expected test failures that don't have a bug annotation? Maybe even something we could integrate into triage-center?
I don't know what triage-center is, but increasing the visibility of failures in web-platform-tests is certainly something that I think I should work on; we are currently letting compat problems slip through unnecessarily. If there is a preferred way to expose that information to developers I'm very interested to hear about it.
As a short term stopgap, you might be interested to know that all upstream PRs are now run through a stability checker that runs the tests both in Firefox and Chrome. This includes test submissions that Google upstreams. So if you look for PRs that you are interested in (e.g. [1] for web-animations) you can get a heads-up about incoming tests with Firefox/Chrome differences (work to add Edge and Safari to this stability checker is in progress, but there are technical difficulties we have to overcome there).
[1] https://github.com/w3c/web-platform-tests/pulls?q=is%3Apr+is%3Aopen+label%3Aweb-animations
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
