-
Notifications
You must be signed in to change notification settings - Fork 417
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
Test failing #484
Comments
That test is not part of the core concurrent-ruby gem, it's part of the Edge gem and can safely be ignored. The code under test won't be packaged with concurrent-ruby. We build three gems out of this repository:
The code being tested by the failing test is part of concurrent-ruby-edge. If you package just the core concurrent-ruby gem you won't have that code. I'm out of town for business today but will be home soon. Once I return home I'll go through our tests and make sure that all tests not in the core gem are tagged so that they can be easily excluded from CI runs. To see what files are in which gem please reference our file map. |
Ok. Thanks. I will skip it in the package for now. |
@jdantonio Hi, when you get time, can you please tag which all tests are part of the core gem? |
Tomorrow is Christmas Eve so I won't be able to get to this for a few days. I hope to be able to do this next week. |
That is fine. For now I will simply disable the failing tests. Happy holidays. :) |
Merged in PR #491. |
Thanks @jdantonio . This is a great help. |
Hi,
I am packaging concurrent-ruby for Debian as part of GitLab packaging and am stuck with a weird test failure. All the tests run fine except one. The log can be seen here - http://paste.debian.net/343198/
Please help me fix it.
The text was updated successfully, but these errors were encountered: