Created attachment 140723 [details] proposed fix

Comment on attachment 140723 [details] proposed fix What's the use-case for this? I'm not opposed to adding this if there's a good benefit, but I'm sensitive to the clutter/usefulness tradeoff. Also, this will need a test. See http://trac.webkit.org/browser/trunk/LayoutTests/fast/harness/resources/results-test.js.

I want this because it provides an "at a glance" way to know if you broke more tests than were already broken when making a change.

(In reply to comment #3) > I want this because it provides an "at a glance" way to know if you broke more tests than were already broken when making a change. I see. That's fine with me. This patch just needs a test then. The existing test may actually cover this, but will need a new expected result. It just runs with run-webkit-tests since it's in the LayoutTests directory.

(In reply to comment #4) > (In reply to comment #3) > > I want this because it provides an "at a glance" way to know if you broke more tests than were already broken when making a change. > > I see. That's fine with me. This patch just needs a test then. The existing test may actually cover this, but will need a new expected result. It just runs with run-webkit-tests since it's in the LayoutTests directory. Hi, I ran the nrwt for this test, and it didn't fail. It seems the existing test doesn't cover this hence I've looked the results-test.js how I could write a test for it, but I've lost in the code :( Could you explain how I should do that?

(In reply to comment #5) > (In reply to comment #4) > > (In reply to comment #3) > > > I want this because it provides an "at a glance" way to know if you broke more tests than were already broken when making a change. > > > > I see. That's fine with me. This patch just needs a test then. The existing test may actually cover this, but will need a new expected result. It just runs with run-webkit-tests since it's in the LayoutTests directory. > > Hi, > I ran the nrwt for this test, and it didn't fail. It seems the existing test doesn't cover this hence I've looked the results-test.js how I could write a test for it, but I've lost in the code :( > Could you explain how I should do that? Take any of the existing runTest calls and add the appropriate assertions that the number of failing tests matches the number of failing tests in the mockResults object. Make sure to cover the testList case and the failingTestsTable case.

Created attachment 142963 [details] proposed fix with unit test

Comment on attachment 142963 [details] proposed fix with unit test Attachment 142963 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/12744154 New failing tests: fast/harness/results.html

Created attachment 142980 [details] Archive of layout-test-results from ec2-cr-linux-02 The attached test failures were seen while running run-webkit-tests on the chromium-ews. Bot: ec2-cr-linux-02 Port: <class 'webkitpy.common.config.ports.ChromiumXVFBPort'> Platform: Linux-2.6.35-28-virtual-x86_64-with-Ubuntu-10.10-maverick

(In reply to comment #8) > (From update of attachment 142963 [details]) > Attachment 142963 [details] did not pass chromium-ews (chromium-xvfb): > Output: http://queues.webkit.org/results/12744154 > > New failing tests: > fast/harness/results.html Interesting. I've updated the expectation for this test and it runs fine locally.

(In reply to comment #10) > (In reply to comment #8) > > (From update of attachment 142963 [details] [details]) > > Attachment 142963 [details] [details] did not pass chromium-ews (chromium-xvfb): > > Output: http://queues.webkit.org/results/12744154 > > > > New failing tests: > > fast/harness/results.html > > Interesting. I've updated the expectation for this test and it runs fine locally. The problem is that there's also a results-expected.txt in platform/win and platform/chromium-win. I'm 99% sure that you can just delete the platform/chromium-win result now that chromium-win no longer falls back to platform/win, but you'll also need to update the platform/win result to keep the test passing on Apple's Win port.

Created attachment 143220 [details] proposed fix with unit test I looked to platform/win for update the expectation but it is really old (2011-10-20). The apple's win bots have "dead" for a long time so I couldn't update it. If the ews doesn't go red I will cq+ it.

Comment on attachment 143220 [details] proposed fix with unit test Clearing flags on attachment: 143220 Committed r117950: <http://trac.webkit.org/changeset/117950>

All reviewed patches have been landed. Closing bug.