RESOLVED FIXED154513
Re-sync W3C HTML/DOM web-platform-tests 
https://bugs.webkit.org/show_bug.cgi?id=154513
Summary Re-sync W3C HTML/DOM web-platform-tests
Chris Dumez
Reported 2016-02-21 09:53:22 PST
Re-sync W3C HTML/DOM web-platform-tests after: https://github.com/w3c/web-platform-tests/pull/2597
Attachments
Patch (41.01 KB, patch)
2016-02-21 10:39 PST, Chris Dumez 		no flags
DetailsFormatted DiffDiff
Patch (48.32 KB, patch)
2016-02-21 13:03 PST, Chris Dumez 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Chris Dumez
Comment 1 2016-02-21 10:39:08 PST
Created attachment 271883 [details] Patch
Chris Dumez
Comment 2 2016-02-21 13:03:52 PST
Created attachment 271886 [details] Patch
WebKit Commit Bot
Comment 3 2016-02-21 17:27:39 PST
Comment on attachment 271886 [details] Patch Clearing flags on attachment: 271886 Committed r196883: <http://trac.webkit.org/changeset/196883>
WebKit Commit Bot
Comment 4 2016-02-21 17:27:44 PST
All reviewed patches have been landed. Closing bug.
youenn fablet
Comment 5 2016-02-24 12:52:13 PST
I plan to resync all wpt tests. Did you use 5a2e4eb7c92bfa91e00465ec1f2922ec3412829a for the html tests?
Chris Dumez
Comment 6 2016-02-24 12:53:54 PST
(In reply to comment #5) > I plan to resync all wpt tests. > Did you use 5a2e4eb7c92bfa91e00465ec1f2922ec3412829a for the html tests? I have been updating tests in a very ad-hoc fashion over the last few weeks, simply by copying tests over from the other repo. I do not know which exact revision I used when I last did a full sync and some of the tests have been updated more recently than that.
youenn fablet
Comment 7 2016-02-26 00:13:21 PST
(In reply to comment #6) > (In reply to comment #5) > > I plan to resync all wpt tests. > > Did you use 5a2e4eb7c92bfa91e00465ec1f2922ec3412829a for the html tests? > > I have been updating tests in a very ad-hoc fashion over the last few weeks, > simply by copying tests over from the other repo. I do not know which exact > revision I used when I last did a full sync and some of the tests have been > updated more recently than that. I see. If you are not using the importer, it might be good to check and update LayoutTests/imported/w3c/resources/ImportExpectations, which defines which tests the importer will skip. That way, this will ensure that when resyncing the whole test suite, some added tests do not get removed inadvertently. The issue remains for tests specific to WebKit and not yet upstreamed to WPT repo. The importer should probably only remove tests that were removed between the old and new revision of the WPT repo.
Note You need to log in before you can comment on or make changes to this bug.