You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mkustermann opened this issue
Oct 28, 2013
· 1 comment
Labels
area-testCross-cutting test issues (use area- labels for specific failures; not used for package:test).type-bugIncorrect behavior (everything from a crash to more subtle misbehavior)
The html/dromaeo_smoke_test test is posting data which is received by the test driver page. The driving page in return assumes that the test is finished and what it got is a DOM, so it'll post the DOM back to test.dart.
But what get's actually posted is not the DOM, but rather some json:
area-testCross-cutting test issues (use area- labels for specific failures; not used for package:test).type-bugIncorrect behavior (everything from a crash to more subtle misbehavior)
The html/dromaeo_smoke_test test is posting data which is received by the test driver page. The driving page in return assumes that the test is finished and what it got is a DOM, so it'll post the DOM back to test.dart.
But what get's actually posted is not the DOM, but rather some json:
FAILED: dart2js-safari release_ia32 html/dromaeo_smoke_test
Expected: Pass
Actual: RuntimeError
CommandOutput[dart2js]:
CommandOutput[safari]:
stdout:
{"command":"inited","data":{"nTests":1}}
stderr:
http://build.chromium.org/p/client.dart/builders/dart2js-safari-mac10.7-1-3-be/builds/1215/steps/dart2js-safari%20tests%20failures/logs/stdio
Marking it as flaky for now.
To make the driver page more robust, we should introduce a special "protocol" and ignore messages posted which don't follow that "protocol".
The test could also be changed to not post data to the opener / driving window page.
The text was updated successfully, but these errors were encountered: