-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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 are broken in release 3.6.2 #10134
Comments
I get the reverse, 3.6.2 did NOT have this issue, but 3.6.3 DOES print this "Failure". |
I'm seeing the same -- 3.6.3 has this failure but 3.6.2 does not. |
Thanks. @faho reckons they pass on his machine as well, but they fail on my local machines and on all CI platforms with 3.6.2. So more digging to be done, but it's way past my bedtime here! |
This test wants to generate a U+FDD2 to see it is not mishandled. To do so, we tried to use sh, which on my system is bash and can do `$'\ufdd2'`. Unfortunately on other systems it might be dash, which won't do that. Since I don't know of a good no-dependency portable way to generate this (I dimly remember python3 being a shim on some systems, so I do not want to invoke it here), we'll just use our own printf. Which is a worse test, we control both parts, but it'll do. Fixes fish-shell#10134
The issue is /bin/sh - on my system that is bash, on Ubuntu and Debian it's dash. And it turns out that dash won't do I would like if we could easily get something else to generate a U+FDD2, but I don't believe there's a good version without introducing a dependency, so we'll just let our printf do it: echo (printf '\ufdd2foo') | string escape
# CHECK: \Xef\Xb7\X92foo That's faho@b2ef44a. Passes on my system and Github Actions. |
This patch fixes the test failure in openSUSE Tumbleweed and Fedora Rawhide, thanks for creating it! Will you create another dot release or should we patch this downstream? |
I'll do a new release tonight. |
David Adam ***@***.***> writes:
I'll do a new release tonight.
Thanks!
|
I thought I'd run the test suite, but it looks like I didn't.
The check is looking for the UTF-8 encoding.
I've already pushed the advisory and the new release, so I can make a 3.6.3 to fix the tests.
The text was updated successfully, but these errors were encountered: