-
Notifications
You must be signed in to change notification settings - Fork 254
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 failures caused by Thread trace output #227
Comments
would prefer that nobody builds packages from this gem ... means more bugs for me + people running old versions without being able to update |
the errors looks kinda weird ... are they reproducible while running a single test case ? |
A couple of packages that Debian ships depend on the parallel gem, so we had to package it too. Would you recommend disabling all tests during build? |
If you want me to run some more tests/debugging, let me know, I would be happy to help. |
idk how to debug remotely ... disable the offending tests or all tests,
since the CI already runs on ubuntu ...
…On Thu, Aug 23, 2018 at 12:36 AM Cédric Boutillier ***@***.***> wrote:
If you want me to run some more tests/debugging, let me know, I would be
happy to help.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#227 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAsZyztyGcOrRs_DzOwYQUP5QdQjYl9ks5uTluNgaJpZM4WDhVT>
.
|
Hi,
When building the package for Debian, the test suite is run. From time to time, a test fails because of the presence of a debug trace, which causes the output to not match the expected result:
Here are two examples of such failures:
or
These traces are certainly not wanted, but maybe the tests should use regexp matches instead of strict equality of strings. What do you think?
The text was updated successfully, but these errors were encountered: