RESOLVED FIXED 122312
Remove Qt features from build and test tools
https://bugs.webkit.org/show_bug.cgi?id=122312
Summary Remove Qt features from build and test tools
Brent Fulgham
Reported 2013-10-03 20:56:08 PDT
Remove the Qt-specific logic in our build scripts and test tools
Attachments
Patch (110.11 KB, patch)
2013-10-03 21:01 PDT, Brent Fulgham
no flags
Revised to pass all script tests (112.84 KB, patch)
2013-10-04 10:16 PDT, Brent Fulgham
no flags
Modified based on dpranke's comments. (112.93 KB, patch)
2013-10-04 10:40 PDT, Brent Fulgham
no flags
Brent Fulgham
Comment 1 2013-10-03 21:01:09 PDT
Brent Fulgham
Comment 2 2013-10-04 09:12:50 PDT
Comment on attachment 213328 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=213328&action=review > Tools/Scripts/webkitpy/common/checkout/baselineoptimizer_unittest.py:147 > 'LayoutTests/platform/mac': '5', rniwa: should this be renumbered to '4'? > Tools/Scripts/webkitpy/common/checkout/baselineoptimizer_unittest.py:150 > 'LayoutTests/platform/mac': '5', rniwa: ditto
Alexey Proskuryakov
Comment 3 2013-10-04 10:01:58 PDT
> rniwa: should this be renumbered to '4'? These are tests, did you try running them?
Brent Fulgham
Comment 4 2013-10-04 10:08:29 PDT
(In reply to comment #3) > > rniwa: should this be renumbered to '4'? > > These are tests, did you try running them? I thought they got run as part of run-webkit-tests, but running "test-webkitpy" I see a few errors. I'll fix and upload a new patch. Thanks for the suggestion!
Brent Fulgham
Comment 5 2013-10-04 10:16:05 PDT
Created attachment 213370 [details] Revised to pass all script tests
Brent Fulgham
Comment 6 2013-10-04 10:17:24 PDT
The patch passes all tests, but I'm still not convinced that the code in "baselineoptimizer_unittest.py" is correct. I feel like the numbers should be reordered to be consecutive.
Dirk Pranke
Comment 7 2013-10-04 10:32:12 PDT
The code in baselineoptimizer_unittest.py is, at best, a bit strange. I don't think it tests what Ojan thought it did (nor did he, once I got him to look at it again), and I eventually rewrote the Blink version almost completely to use a mock filesystem; it ended up shorter and much clearer. I don't think you can just copy the Blink version over, though, since the fallback graph is now pretty different between WebKit and Blink, but you might take a look at it at some point and adapt it instead. The numbers don't need to be consecutive, just different (to indicate which results should match and which shouldn't). You might find having them be consecutive makes things at least clearer, though.
Brent Fulgham
Comment 8 2013-10-04 10:40:51 PDT
Created attachment 213375 [details] Modified based on dpranke's comments.
Hugo Parente Lima
Comment 9 2013-10-04 10:43:53 PDT
*** Bug 122330 has been marked as a duplicate of this bug. ***
Hugo Parente Lima
Comment 10 2013-10-04 10:48:56 PDT
After this patch I think nobody will be using old-run-webkit-tests.
Dirk Pranke
Comment 11 2013-10-04 10:56:25 PDT
(In reply to comment #10) > After this patch I think nobody will be using old-run-webkit-tests. I think Apple is still using ORWT internally for the iOS port, unless something has changed.
WebKit Commit Bot
Comment 12 2013-10-04 11:18:56 PDT
Comment on attachment 213375 [details] Modified based on dpranke's comments. Clearing flags on attachment: 213375 Committed r156895: <http://trac.webkit.org/changeset/156895>
WebKit Commit Bot
Comment 13 2013-10-04 11:18:58 PDT
All reviewed patches have been landed. Closing bug.
Ryosuke Niwa
Comment 14 2013-10-04 11:24:18 PDT
We should just get rid of the baseline optimizer. It's already broken.
Note You need to log in before you can comment on or make changes to this bug.