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 failing in Fedora #198
Comments
@pvalena I think these tests were introduced to test If you're using It might be possible to skip these tests if Nokogiri is compiled against system libraries; maybe @rgrove can comment on whether he'd be open to a change like that in the test suite. |
Ah yes, we try to avoid the use of bundled libraries. I was hoping this was not the case. Thanks for the explanation! |
Thanks for the assist, @flavorjones! You're right, these failures do appear to be related to the tests expecting the output that Nokogiri's bundled libxml2 would generate. @pvalena I'd be open to a patch that alters the behavior of these tests either by detecting that a non-patched libxml2 is being used and asserting different output as appropriate, or by skipping these tests when a specific env var is set. But if you already have an easier way to work around this on your end, that works too. 😄 |
Actually, my solution would be to ignore the failures. But as I'll probably avoid owning the package in Fedora (I currently don't have much use for it), it doesn't matter now. @rgrove thanks! |
Hello, I've tried to bring back sanitize 5.1.0 into Fedora, but it seems some tests are failing:
The whole package build log can be found here:
https://download.copr.fedorainfracloud.org/results/pvalena/rubygems/fedora-rawhide-x86_64/01352482-rubygem-sanitize/build.log.gz
It also fails on all Fedoras and EL+8:
https://copr.fedorainfracloud.org/coprs/pvalena/rubygems/build/1352482/
Versions:
ruby x86_64 2.7.1-130.fc33 fedora 41 k
rubygem-crass noarch 1.0.4-5.fc33 copr_base 18 k
rubygem-minitest noarch 5.14.0-201.fc32 fedora 45 k
rubygem-nokogiri x86_64 1.10.9-1.fc33.1 copr_base 128 k
rubygem-nokogumbo x86_64 2.0.2-1.fc33.1 copr_base 300 k
Let me know if I can do anything else to debug/workaround this issue, or if you need more info.
The text was updated successfully, but these errors were encountered: