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.

Sign up for GitHub

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

Jump to bottom

JRUBY-5283 Thread specs fail sporadically on Travis #1011

Closed
BanzaiMan opened this issue Sep 13, 2013 · 2 comments
Closed

JRUBY-5283 Thread specs fail sporadically on Travis #1011

BanzaiMan opened this issue Sep 13, 2013 · 2 comments
Labels
core
Milestone
Non-Release

Comments

@BanzaiMan
Copy link
Member

See:
https://travis-ci.org/jruby/jruby/jobs/11307141#L544
https://travis-ci.org/jruby/jruby/jobs/11307142#L573

http://bugs.jruby.org/5283

These pass on my local machines, but they tend to fail with high probability on Travis. I am not sure why. Maybe it is Linux-specific, but I haven't tested it.
@BanzaiMan
Copy link
Member Author

See 6b91220.

mbj pushed a commit to mbj/jruby that referenced this issue Nov 8, 2013
@BanzaiMan
Deactivate JRUBY-5283 regression specs
6b91220 
These seem to fail on Travis, so I'm deactivating them for Travis's
sake.

See jruby#1011
@kares kares added this to the Non-Release milestone Jun 22, 2017
kares added a commit to kares/jruby that referenced this issue Jun 23, 2017
@kares
[test] re-surrect regression spec disabled at jruby#1011
027de6d
kares added a commit to kares/jruby that referenced this issue Jun 23, 2017
@kares
[test] re-surrect regression spec disabled at jruby#1011
3a4f90f
kares added a commit that referenced this issue Jun 23, 2017
@kares
[test] re-surrect regression spec disabled at #1011
718cb7d
@kares
Copy link
Member

kares commented Jun 23, 2017

and its back after almost 4y 🥀

@kares kares closed this as completed Jun 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
core
Projects
None yet
Milestone
Non-Release
Development

No branches or pull requests
2 participants
@BanzaiMan @kares