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

Travis CI failure - tests fail to start #7193

Closed
lilleyse opened this issue Oct 26, 2018 · 4 comments · Fixed by #7194
Closed

Travis CI failure - tests fail to start #7193

lilleyse opened this issue Oct 26, 2018 · 4 comments · Fixed by #7194

Comments

@lilleyse
Copy link
Contributor

Seems to be a recent failure.

https://api.travis-ci.org/v3/job/446471076/log.txt

[22:05:12] Starting 'test'...
25 10 2018 22:05:12.939:INFO [framework.detect-browsers]: Detecting browsers is disabled. The browsers of the browsers array are used.
25 10 2018 22:05:15.023:INFO [karma]: Karma v2.0.5 server started at http://0.0.0.0:9876/
25 10 2018 22:05:15.024:INFO [launcher]: Launching browser ChromeCI with unlimited concurrency
25 10 2018 22:05:15.029:INFO [launcher]: Starting browser ChromeHeadless
25 10 2018 22:05:16.485:INFO [HeadlessChrome 0.0.0 (Linux 0.0.0)]: Connected on socket FYUQ78QJTOVvdCgIAAAA with id 46055948
HeadlessChrome 0.0.0 (Linux 0.0.0) ERROR LOG: 'DEPRECATION:', 'Setting specFilter directly on Env is deprecated, please use the specFilter option in `configure`'
25 10 2018 22:05:46.615:WARN [HeadlessChrome 0.0.0 (Linux 0.0.0)]: Disconnected (1 times), because no message in 30000 ms.
HeadlessChrome 0.0.0 (Linux 0.0.0) ERROR
  Disconnected, because no message in 30000 ms.
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 0 of 0 DISCONNECTED (30.131 secs / 0 secs)

I've also seen it fail for HeadlessFirefox.

@likangning93
Copy link
Contributor

likangning93 commented Oct 26, 2018

I'm seeing this very consistently in #7168 as well.

[EDIT] https://api.travis-ci.org/v3/job/446467943/log.txt

@hpinkos
Copy link
Contributor

hpinkos commented Oct 26, 2018

Ditto. I started to see this yesterday

@hpinkos
Copy link
Contributor

hpinkos commented Oct 26, 2018

I just saw this same problem in one of our other projects too.
@mramato Could this have to do with Jasmine releasing a new version 21 hours ago? https://github.com/jasmine/jasmine/releases

@hpinkos
Copy link
Contributor

hpinkos commented Oct 26, 2018

Yep. It's likely jasmine/jasmine#1617

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants