Syncing w3c/web-platform-tests as described at http://www.chromium.org/blink/importing-the-w3c-tests results in new test failures. This bug is the initial tracking of these extra failures. Individual test failures should probably be farmed out to separate bugs as investigation proceeds.
In addition to updating 10 paths in TestExpectations due to changes upstream to web-platform-tests/mediacapture-streams, we have three new failures listed in TestExpectations, six new failures requiring -expected.txt files, and four tests whose -expected.txt files needed to be updated.
New TestExpectations entries
- imported/web-platform-tests/mediacapture-streams/GUM-deny.html [ Failure ]
- imported/web-platform-tests/mediacapture-streams/MediaDevices-getUserMedia.html [ Failure ]
- imported/web-platform-tests/mediacapture-streams/MediaStream-MediaElement-srcObject.html [ Failure ]
New -expected files
- imported/web-platform-tests/dom/events/Event-dispatch-bubbles-false-expected.txt
- imported/web-platform-tests/dom/lists/DOMTokenList-value-expected.txt
- imported/web-platform-tests/html/semantics/interactive-elements/the-details-element/toggleEvent-expected.txt
- imported/web-platform-tests/html/semantics/scripting-1/the-script-element/script-charset-01-expected.txt
- imported/web-platform-tests/html/semantics/scripting-1/the-script-element/script-charset-02-expected.txt
- imported/web-platform-tests/html/webappapis/scripting/events/event-handler-processing-algorithm-expected.txt
Updated -expected files
- imported/web-platform-tests/dom/interfaces-expected.txt
- imported/web-platform-tests/dom/nodes/Element-classlist-expected.txt
- imported/web-platform-tests/dom/nodes/Node-replaceChild-expected.txt
- imported/web-platform-tests/dom/nodes/attributes-expected.txt
perkj, keishi, tkent: Could you please triage these test failures and file bugs as appropriate to track fixing these issues? This bug number is associated with the three new TestExpectations entries, so if new bugs are opened for those, that TestExpectations line should be similarly updated. Ideally this bug would then be closed.
I'm unassigning myself as owner because I don't have time at the moment to keep an eye on progress of this bug. I'm not sure who should be responsible for it going forward. tkent/jsbell: do you have a suggestion on this?
Is this bug a blanket bug for all web-platform-tests failures?
Or just dom/html?
Note, there's another bug for failures of automatically-imported tests (bug 626703) - Should these be merged together?
Side note: There is an increasingly large number of test expectation lines for auto-imported tests, which doesn't seem sustainable -- but in general, it might be hard to keep up with all failures in new tests since the tests are automatically imported and it's not necessarily guaranteed that we care about all of the imported tests.
I'm not really sure what to do about this now - it seems like the scalable solution will be to:
(1) Start filing separate bugs for separate directories in wpt, and have separate people in separate teams triage most of the failures?
(2) Or maybe if we really don't care about failures in automatically imported tests, maybe the expectations for these tests shouldn't be in TestExpectations?
Re #11:
I suspect this bug is obsolete given the existence of issue 626703.
When I started looking at some more Web Animations API work this week I realised that the auto-import had created a bunch of TestExpectations entries that I should tidy up (https://codereview.chromium.org/2796313002). Perhaps if I'd been paying more attention to the auto-imports I would have realised this sooner, but I think separate bugs and/or separate TestExpectations files for separate directories in wpt would be a good idea to keep these coming to the attention of the animations team.
It seems that with the owners information in W3CImportExpectations and the efforts like https://codereview.chromium.org/2751113002/ and https://codereview.chromium.org/2783203003/ it should be feasible to file bugs in suitable components for this purpose?
Yep, it should be feasible, and that would definitely help us keep it more organized! This is related to bug bug 663383 and bug 676672 .
Right now there are 368 auto-added expectations in TestExpectations (associated with bug 626703) and ideally owners/teams should go through relevant entries and see whether they should be associated with other bugs, which would be easier if these were organized better in TestExpectations...
Comment 1 by bugdroid1@chromium.org
, Apr 8 2016