-
Notifications
You must be signed in to change notification settings - Fork 60
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
tests fail when built with only feature std #366
Comments
Oh, and full credit for the above patch goes to @plugwash - I am simply forwarding here what he offered for the Debian packaging. |
Thanks for taking the time to get this to work. This library has a long history, so I'm not surprised there are a few bumps in the road. These two features have been considered always available to the tests. Unit tests have to run with the I suppose the |
Hello again! I'm finally looking through these issues again (I needed more of a break than first expected), and just want to know if this is a blocking issue for you. I'm most likely not gating the test functions on |
Since only tests fail, it is not exactly blocking: I do have the option of skipping tests failing due to this. Obvious problem in that is that I may mask detection of other bugs by doing so. What I do now is apply the patch, and I intent on attempting to massage that patch to match newer releases for as long as I can - and if at some point I am no longer able to keep that hack of mine alive and you haven't addressed this issue by then, I will shift the the lesser preferred option of sloppily skipping tests that fail. Thanks for all your work on this. |
Hmm, that's not ideal. 😬 Are the tests only running the features one by one, or do they also try combinations? I'm asking because it's likely that some tests will need both If it's not possible for you to run the tests with |
It is possible for me to do whatever adjustments to tests needed - including always adding Sorry that I seemingly failed to get my point across: I am flexible, and as a last resort I can simply skip tests. |
...and to answer your concrete question: No, what I practice currently is not a full combinational matrix of features, only each single feature done alone, and all features, and no features. |
Thanks that's good to know, so I know what's expected to work. 👍 If it's not too much of a hassle, I think it's a safer bet to include |
Like I mentioned in the PR, this patch should be unnecessary after the next release. Just keep in mind that a couple of tests use both |
When built without default features, only with std feature, a bunch of tests fail.
This can be fixed by adding appropriate feature guards, like this:
The text was updated successfully, but these errors were encountered: