Skip to content
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

Tests involving selection and ranges time out on dart2js-chrome-win7 #15140

Closed
peter-ahe-google opened this issue Nov 18, 2013 · 4 comments
Closed
Labels
area-infrastructure type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@peter-ahe-google
Copy link
Contributor

From http://build.chromium.org/p/client.dart/builders/dart2js-chrome-win7-be/builds/1205/steps/dart2js-chrome%20tests%20failures/logs/stdio

@@@BUILD_STEP dart2js-chrome tests failures@@@

FAILED: dart2js-chrome release_ia32 html/range_test/functional
Expected: Pass
Actual: Timeout
CommandOutput[dart2js]:
CommandOutput[chrome]:

stdout:
Dom could not be fetched, since the test timed out.

stderr:
This test timed out. The delay until the test actually started was: 0:00:00.100010.

BrowserOutput while running the test (* EXPERIMENTAL *):
BrowserOutput.stdout:

BrowserOutput.stderr:

To retest, run: e:\b\build\slave\dart2js-chrome-win7-be\build\dart\tools\testing\bin\windows\dart.exe /e:/b/build/slave/dart2js-chrome-win7-be/build/dart/tools/testing/dart/http_server.dart -p 49351 -c 49352 --build-directory=e:\b\build\slave\dart2js-chrome-win7-be\build\dart\build\ReleaseIA32 --runtime=chrome

Command[dart2js]: build\ReleaseIA32\dart-sdk\bin\dart2js.bat --package-root=build/ReleaseIA32/packages/ --out=e:/b/build/slave/dart2js-chrome-win7-be/build/dart/build/ReleaseIA32/generated_compilations/dart2js/tests_html_range_test/test.js /e:/b/build/slave/dart2js-chrome-win7-be/build/dart/tests/html/range_test.dart
Took 0:00:09.201000

Command[chrome]: \e:\b\build\slave\dart2js-chrome-win7-be\build\dart\tools\testing\bin\windows\dart.exe tools/testing/dart/launch_browser.dart chrome http://127.0.0.1:49351/root_build/generated_tests/dart2js-chrome/tests_html_range_test/test.html?crossOriginPort=49352&group=functional
Took 0:01:00.100009

Short reproduction command (experimental):
    python tools/test.py -mrelease -cdart2js -rchrome --use-sdk --write-debug-log -t60 html/range_test/functional

From http://build.chromium.org/p/client.dart/builders/dart2js-chrome-win7-be/builds/1202/steps/dart2js-chrome%20tests%20failures/logs/stdio

FAILED: dart2js-chrome release_ia32 html/range_test/functional
Expected: Pass
Actual: Timeout
CommandOutput[dart2js]:
CommandOutput[chrome]:

stdout:
Dom could not be fetched, since the test timed out.

stderr:
This test timed out. The delay until the test actually started was: 0:00:00.100010.

BrowserOutput while running the test (* EXPERIMENTAL *):
BrowserOutput.stdout:

BrowserOutput.stderr:

To retest, run: e:\b\build\slave\dart2js-chrome-win7-be\build\dart\tools\testing\bin\windows\dart.exe /e:/b/build/slave/dart2js-chrome-win7-be/build/dart/tools/testing/dart/http_server.dart -p 49351 -c 49352 --build-directory=e:\b\build\slave\dart2js-chrome-win7-be\build\dart\build\ReleaseIA32 --runtime=chrome

Command[dart2js]: build\ReleaseIA32\dart-sdk\bin\dart2js.bat --package-root=build/ReleaseIA32/packages/ --out=e:/b/build/slave/dart2js-chrome-win7-be/build/dart/build/ReleaseIA32/generated_compilations/dart2js/tests_html_range_test/test.js /e:/b/build/slave/dart2js-chrome-win7-be/build/dart/tests/html/range_test.dart
Took 0:00:09.201000

Command[chrome]: \e:\b\build\slave\dart2js-chrome-win7-be\build\dart\tools\testing\bin\windows\dart.exe tools/testing/dart/launch_browser.dart chrome http://127.0.0.1:49351/root_build/generated_tests/dart2js-chrome/tests_html_range_test/test.html?crossOriginPort=49352&group=functional
Took 0:01:00.100009

Short reproduction command (experimental):
    python tools/test.py -mrelease -cdart2js -rchrome --use-sdk --write-debug-log -t60 html/range_test/functional

@blois
Copy link
Contributor

blois commented Nov 18, 2013

I'm unable to repro this locally and don't see any reason why this would timeout. I believe this test has been stable for a while.

Did something change in the test framework?


cc @ricowind.
cc @mkustermann.

@DartBot
Copy link

DartBot commented Nov 19, 2013

This comment was originally written by kuste...@chromium.org


Not that I'm aware of.

There were smaller things, like removing selenium related code (which wasn't used anymore), etc -- but nothing that could cause timeouts AFAIK.

Just FYI: I'll be working soon on getting more information for these timeouts.

@blois
Copy link
Contributor

blois commented Nov 19, 2013

Moving to test as it appears that random tests are timing out on Chrome, not just HTML.


Removed Area-HTML label.
Added Area-Test label.

@ricowind
Copy link
Contributor

Removed Area-Test label.
Added Area-Infrastructure label.

@kevmoo kevmoo added type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) and removed priority-unassigned labels Feb 29, 2016
@sortie sortie closed this as not planned Won't fix, can't repro, duplicate, stale Jul 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infrastructure type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Development

No branches or pull requests

6 participants