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

Possible browser compatibility regressions #2104

Closed
Krinkle opened this issue Feb 20, 2015 · 2 comments
Closed

Possible browser compatibility regressions #2104

Krinkle opened this issue Feb 20, 2015 · 2 comments
Assignees
Labels

Comments

@Krinkle
Copy link
Member

Krinkle commented Feb 20, 2015

Due to impending purging of TestSwarm data (while we migrate the app to a new server), here's data about possible regressions found in the last 7 days.

I've let these failures re-run to filter out false negatives. Here's what's left:

jQuery

screen shot 2015-02-20 at 02 16 15

  • IE8 started failing between 7cd9a36 and 2380028
    » 255 test failures in effects module. All other modules passed.
  • IE10 and IE11 started failing between 2380028 and 9368a8c
    » 1 test failure in dimensions module. All other modules passed.

jQuery Weekly

screen shot

  • Android 4.3 started failing between 8b6aeae and f2ea60c.
    » the traversing module timed out repeatedly. All other modules passed.
@markelog markelog self-assigned this Feb 20, 2015
@markelog
Copy link
Member

Will check them out

@timmywil timmywil added this to the 3.0.0 milestone Mar 9, 2015
@timmywil
Copy link
Member

This issue is no longer necessary. We've had several runs since and should be keeping our eyes on swarm failures at all times. I'll keep a reminder in the meeting minutes and won't release until we've got all green. Thanks!

@dmethvin dmethvin removed this from the 3.0.0 milestone Jan 7, 2016
@lock lock bot locked as resolved and limited conversation to collaborators Jun 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Development

No branches or pull requests

4 participants