New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Swarm has a lot of test suppressions #14523
Comments
Added this to the Later milestone. |
Removed Area-HTML label. |
Removed this from the Later milestone. |
Removed Oldschool-Milestone-Later label. |
This comment was originally written by whesse@chromium.org html/websql_test/functional has started passing after the iframe containing it comes from the same server as the containing page (the same port number). Maybe it was a cross-origin issue. |
WebSQL tests seem to be ok and is deprecated. The swarm testing in general doesn't seem to be in great shape. Right now it fails for me on Chrome, passes on Dartium and Firefox, and passes on Safari, but only after putting alarming messages on the console. Swarm doesn't work well with current dev infrastructure, it's not a package, the README for running it is wrong, but Stephen doesn't want to change Swarm any more than necessary, and it's not a high priority. Removed Type-Defect, Priority-Unassigned, Area-Library, Library-Html labels. |
Set owner to @rakudrama. |
We don't run swarm tests anymore. |
The following tests seem to have started failing after running these tests in an iframe instead of a new browser window.
dart2js-safari:
samples/swarm/test/swarm_test (http://build.chromium.org/p/client.dart/builders/dart2js-safari-mac10.7-3-3-be/builds/1218/steps/dart2js-safari%20tests%20failures/logs/stdio)
html/websql_test/functional (http://build.chromium.org/p/client.dart/builders/dart2js-safari-mac10.7-2-3-be/builds/1164/steps/dart2js-safari%20tests%20failures/logs/stdio)
dart2js-chrome:
samples/swarm/test/swarm_test (build.chromium.org/p/client.dart/builders/dart2js-chrome-mac10.7-be/builds/900/steps/dart2js-chrome%20tests%20failures/logs/stdio)
@blois/efortuna:
Do these tests have the requirement that they run in a new window?
Are the failures legitimate?
The text was updated successfully, but these errors were encountered: