-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Fix utf8 tests #8192
Fix utf8 tests #8192
Conversation
Codecov Report
@@ Coverage Diff @@
## master #8192 +/- ##
=========================================
Coverage ? 41.58%
=========================================
Files ? 488
Lines ? 65211
Branches ? 0
=========================================
Hits ? 27116
Misses ? 34607
Partials ? 3488
Continue to review full report at Codecov.
|
how about to set a locale on tests? |
@lunny As I understand it the problem is the compiler's locale, not the actual code. When the compiler parses the strings to generate code, it's got rules and defaults to deal with invalid data that are (or should be) based in the locale. What we could do is to set a LOCALE in the Makefile to force one during compilation. Anyway, with the changes I've made in this PR that shouldn't be necessary, as all the strings are generated from bytes in the code and I've attempted to isolate all the conflicting strings as much as possible. The compiler's locale should no longer affect the generated code nor the test run. |
ping LG-TM bot |
modules/charset/
tests have been failing randomly. My guess, once again, is the LOCALE on the CI server might be producing diferent compilation results when the compiler parses the strings.This time around I've eliminated all but the simplest string literals, e.g.:
changed into
I hope this is the solution. Otherwise, I'd recommend just removing all the UTF8 test.