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

polymer tests timeout in windows? #13260

Closed
sigmundch opened this issue Sep 11, 2013 · 20 comments
Closed

polymer tests timeout in windows? #13260

sigmundch opened this issue Sep 11, 2013 · 20 comments
Labels
area-pkg Used for miscellaneous pkg/ packages not associated with specific area- teams. P1 A high priority bug; for example, a single project is unusable or has many test failures

Comments

@sigmundch
Copy link
Member

Seems like some polymer tests are failing with timeouts in FF and Chrome.

Need to investigate more.

@sigmundch
Copy link
Member Author

Added this to the M8 milestone.

@sigmundch
Copy link
Member Author

Added Library-ShadowDOM label.

@sigmundch
Copy link
Member Author

Removed this from the M8 milestone.
Added this to the Later milestone.

@sigmundch
Copy link
Member Author

Removed this from the Later milestone.
Added this to the M9 milestone.

@clayberg
Copy link

Removed this from the M9 milestone.
Added this to the 1.1 milestone.

@mkustermann
Copy link
Member

The timeouts happened due to a popup of IE9 warning that the site uses Java.

The issue has been fixed, on the bot, the following three tests are left which refer to this bug -- they are failing:

polymer/test/bind_mdv_test: RuntimeError # Issue #14412, 13260
polymer/test/custom_event_test: RuntimeError # Issue #13260
polymer/test/noscript_test: RuntimeError # Issue #13260

@sigmundch
Copy link
Member Author

wow - thanks Martin for the update! Those timeouts have been a mystery for a while.

@sigmundch
Copy link
Member Author

Removed this from the 1.1 milestone.
Added this to the 1.2 milestone.

@floitschG
Copy link
Contributor

noscript_test is flaky. Sometimes passes.
I'm updating the status file.

@anders-sandholm
Copy link
Contributor

Removed Library-ShadowDOM label.
Added Pkg-ShadowDOM label.

@jmesserly
Copy link

looks like only polymer/test/noscript test is left.

I wonder if it is more reliable on IE10/11? IE9 didn't have reliable timing primitives whereas I think 10+ does. (and Polymer doesn't support IE9 anymore so status on IE9 should be a non-issue)


Removed this from the 1.2 milestone.
Added this to the Later milestone.
Removed Pkg-ShadowDOM label.

@jmesserly
Copy link

Removed Area-Polymer label.
Added Pkg-Polymer, Area-Pkg labels.

@sigmundch
Copy link
Member Author

Added Polymer-P-2 label.

@sigmundch
Copy link
Member Author

Removed this from the Later milestone.

@sigmundch
Copy link
Member Author

Removed Polymer-P-2 label.
Added Polymer-Milestone-Later label.

@sigmundch
Copy link
Member Author

Removed Polymer-Milestone-Later label.
Added PolymerMilestone-Later label.

@kasperl
Copy link

kasperl commented Jul 10, 2014

Added this to the 1.6 milestone.

@sigmundch
Copy link
Member Author

Removed this from the 1.6 milestone.

@kasperl
Copy link

kasperl commented Aug 6, 2014

Added this to the 1.6 milestone.

@sigmundch sigmundch added Type-Defect P1 A high priority bug; for example, a single project is unusable or has many test failures area-pkg Used for miscellaneous pkg/ packages not associated with specific area- teams. labels Aug 6, 2014
@DartBot DartBot closed this as completed Jun 4, 2015
@DartBot
Copy link

DartBot commented Jun 5, 2015

This issue has been moved to dart-archive/polymer-dart#78.

@kevmoo kevmoo removed the triaged label Mar 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-pkg Used for miscellaneous pkg/ packages not associated with specific area- teams. P1 A high priority bug; for example, a single project is unusable or has many test failures
Projects
None yet
Development

No branches or pull requests

9 participants