-
Notifications
You must be signed in to change notification settings - Fork 3
Update to libtidy 5.6.0 #2
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
Comments
Thanks for the ping, @cmb69. The version 5.6.0 caused some tests to fail in PHP last time I tried it, so I was basically waiting for a version up. I'll check to apply some patches to 5.4.0 first, at least for use with the stable branches. Thanks. |
@weltling Hmm, it seems all ext/tidy/tests/ are passing on Linux with libtidy 5.6.0 (even when run with valgrind), but of course there may be issues. At least https://bugs.php.net/bug.php?id=76683 is unfortunate. PS: sorry! I've tested with their current HEAD (2018/04/27). Will have a look at 5.6.0 later. |
I've just tried again, but nothing changed.
I see also that i've fixed one test back then http://git.php.net/?p=php-src.git;a=commitdiff;h=83a77383b92d8b1b1a5c141c10e9342aa64b1d92 . I'd tend to applying a patch to 5.4.0 in this case, if one can find one. Thanks. |
I can confirm that ext/tidy/tests/020.phpt fails with libtidy 5.6.0 (the only failing test).
I've applied htacg/tidy-html5#622 (only clean.c), but the segfault remains. Phew! |
Heh, that's itchy. Perhaps some follow up patch fixes the test issue, then upgrading to 5.6.0 could work out. I'll be able to check through the tidy repository close to weekend. Another course of action might be to take some untagged 5.7.x or downgrade to previous 5.2.0. Thanks. |
Applying htacg/tidy-html5@67eaeb6 (no conflicts) to libtidy 5.6.0 lets all tidy tests succeed again (without memory leaks). Might be the best way forward for now. |
Many thanks for the research, Christoph! I'll check and build it next days so it can go into staging. Thanks. |
The upgraded lib has been put into staging as discussed. Thanks! |
Great! Thanks, Anatol. |
Otherwise users might hit https://bugs.php.net/bug.php?id=76992 and maybe other issues.
The text was updated successfully, but these errors were encountered: