Created attachment 254369[details]
Archive of layout-test-results from ews104 for mac-mavericks-wk2
The attached test failures were seen while running run-webkit-tests on the mac-wk2-ews.
Bot: ews104 Port: mac-mavericks-wk2 Platform: Mac OS X 10.9.5
Created attachment 254372[details]
Archive of layout-test-results from ews101 for mac-mavericks
The attached test failures were seen while running run-webkit-tests on the mac-ews.
Bot: ews101 Port: mac-mavericks Platform: Mac OS X 10.9.5
Created attachment 263690[details]
Archive of layout-test-results from ews101 for mac-mavericks
The attached test failures were seen while running run-webkit-tests on the mac-ews.
Bot: ews101 Port: mac-mavericks Platform: Mac OS X 10.9.5
Created attachment 263692[details]
Archive of layout-test-results from ews107 for mac-mavericks-wk2
The attached test failures were seen while running run-webkit-tests on the mac-wk2-ews.
Bot: ews107 Port: mac-mavericks-wk2 Platform: Mac OS X 10.9.5
Created attachment 263693[details]
Archive of layout-test-results from ews112 for mac-yosemite
The attached test failures were seen while running run-webkit-tests on the mac-debug-ews.
Bot: ews112 Port: mac-yosemite Platform: Mac OS X 10.10.5
Comment on attachment 263723[details]
Skipping import of failing tests
View in context: https://bugs.webkit.org/attachment.cgi?id=263723&action=review> LayoutTests/imported/w3c/ChangeLog:8
> + * resources/ImportExpectations: skipping import of some XHR tests that are failing or timing out.
Why not skip running them instead of skip importing them?
> LayoutTests/TestExpectations:354
> +imported/w3c/web-platform-tests/XMLHttpRequest/xmlhttprequest-timeout-aborted.html [ Slow ]
> +imported/w3c/web-platform-tests/XMLHttpRequest/xmlhttprequest-timeout-abortedonmain.html [ Slow ]
> +imported/w3c/web-platform-tests/XMLHttpRequest/xmlhttprequest-timeout-overrides.html [ Slow ]
> +imported/w3c/web-platform-tests/XMLHttpRequest/xmlhttprequest-timeout-overridesexpires.html [ Slow ]
> +imported/w3c/web-platform-tests/XMLHttpRequest/xmlhttprequest-timeout-simple.html [ Slow ]
> +imported/w3c/web-platform-tests/XMLHttpRequest/xmlhttprequest-timeout-synconmain.html [ Slow ]
> +imported/w3c/web-platform-tests/XMLHttpRequest/xmlhttprequest-timeout-twice.html [ Slow ]
> +imported/w3c/web-platform-tests/XMLHttpRequest/xmlhttprequest-timeout-worker-aborted.html [ Slow ]
> +imported/w3c/web-platform-tests/XMLHttpRequest/xmlhttprequest-timeout-worker-overrides.html [ Slow ]
> +imported/w3c/web-platform-tests/XMLHttpRequest/xmlhttprequest-timeout-worker-overridesexpires.html [ Slow ]
> +imported/w3c/web-platform-tests/XMLHttpRequest/xmlhttprequest-timeout-worker-simple.html [ Slow ]
> +imported/w3c/web-platform-tests/XMLHttpRequest/xmlhttprequest-timeout-worker-synconworker.html [ Slow ]
> +imported/w3c/web-platform-tests/XMLHttpRequest/xmlhttprequest-timeout-worker-twice.html [ Slow ]
This seems like a problem. Is there any trickier way we can test timeouts without slowing down our testing like this? Long term it’s not good to let these start creeping in.
(In reply to comment #17)
> Comment on attachment 263723[details]
> Skipping import of failing tests
>
> View in context:
> https://bugs.webkit.org/attachment.cgi?id=263723&action=review
>
> > LayoutTests/imported/w3c/ChangeLog:8
> > + * resources/ImportExpectations: skipping import of some XHR tests that are failing or timing out.
>
> Why not skip running them instead of skip importing them?
It could be done that way too.
These bugs are failing for various reasons.
For instance, some of them use URLs like www2.localhost which should be ok and served as 127.0.0.1 but are blocked by WTR (and probably unresolvable too).
Some tests are working in some environments but not others.
I thought it would be nicer to import them (as [ Skip ] or not) with proper bugs attached to them.
>
> > LayoutTests/TestExpectations:354
> > +imported/w3c/web-platform-tests/XMLHttpRequest/xmlhttprequest-timeout-aborted.html [ Slow ]
> > +imported/w3c/web-platform-tests/XMLHttpRequest/xmlhttprequest-timeout-abortedonmain.html [ Slow ]
> > +imported/w3c/web-platform-tests/XMLHttpRequest/xmlhttprequest-timeout-overrides.html [ Slow ]
> > +imported/w3c/web-platform-tests/XMLHttpRequest/xmlhttprequest-timeout-overridesexpires.html [ Slow ]
> > +imported/w3c/web-platform-tests/XMLHttpRequest/xmlhttprequest-timeout-simple.html [ Slow ]
> > +imported/w3c/web-platform-tests/XMLHttpRequest/xmlhttprequest-timeout-synconmain.html [ Slow ]
> > +imported/w3c/web-platform-tests/XMLHttpRequest/xmlhttprequest-timeout-twice.html [ Slow ]
> > +imported/w3c/web-platform-tests/XMLHttpRequest/xmlhttprequest-timeout-worker-aborted.html [ Slow ]
> > +imported/w3c/web-platform-tests/XMLHttpRequest/xmlhttprequest-timeout-worker-overrides.html [ Slow ]
> > +imported/w3c/web-platform-tests/XMLHttpRequest/xmlhttprequest-timeout-worker-overridesexpires.html [ Slow ]
> > +imported/w3c/web-platform-tests/XMLHttpRequest/xmlhttprequest-timeout-worker-simple.html [ Slow ]
> > +imported/w3c/web-platform-tests/XMLHttpRequest/xmlhttprequest-timeout-worker-synconworker.html [ Slow ]
> > +imported/w3c/web-platform-tests/XMLHttpRequest/xmlhttprequest-timeout-worker-twice.html [ Slow ]
>
> This seems like a problem. Is there any trickier way we can test timeouts
> without slowing down our testing like this? Long term it’s not good to let
> these start creeping in.
These tests are marked as slow (<meta name=timeout content=long>).
In the WPT framework, testharness.js will check this meta tag, and would use a long timeout where necessary.
In current WebKit test framework, we cannot do otherwise than marking these tests as Slow in TestExpectations, at least at first import to reduce the risk of flakiness.
Once they will be run several times, we may be able to remove [ Slow ] for some bots.
Also, these tests are updated versions of LayoutTests/http/tests/xmlhttprequest/timeout/ which are often flaky currently on WebKit bots.
One reason may be that these tests use various XHR timeout values between 200ms and 1s.
WPT tests increased some XHR timeout values to 5s, which is close to some bots regular test timeout.
2015-03-02 09:31 PST, youenn fablet
2015-06-05 11:13 PDT, youenn fablet
2015-06-05 11:38 PDT, Build Bot
2015-06-05 12:11 PDT, Build Bot
2015-10-21 09:13 PDT, youenn fablet
2015-10-21 10:01 PDT, Build Bot
2015-10-21 10:04 PDT, Build Bot
2015-10-21 10:08 PDT, Build Bot
2015-10-21 10:18 PDT, youenn fablet
2015-10-21 11:09 PDT, youenn fablet
2015-10-21 13:16 PDT, youenn fablet