-
Notifications
You must be signed in to change notification settings - Fork 2k
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
murdock and tests using utf-8
characters
#11691
Comments
Can you test on your developer machine if they work with |
And maybe test if adding "export LANG=C.UTF-8" to the top of |
Let's keep this issue seperate. It is a webserver configuration issue and not related to utf-8, but to non-utf-8 being present in the board's output. |
I think
Will try in A good question being where should it be set by default ?
Agreed it is webserver configuration. I put it here if the locale configuration should have been something configured server side. The issue is also present if only |
Locally I successfully tested
with diff --git a/Makefile.include b/Makefile.include
index f9ed21b6a..149ac6d78 100644
--- a/Makefile.include
+++ b/Makefile.include
@@ -582,6 +582,7 @@ reset:
.PHONY: test test/available
TESTS ?= $(foreach file,$(wildcard $(APPDIR)/tests/*[^~]),\
$(shell test -f $(file) -a -x $(file) && echo $(file)))
+test: export LC_ALL=C.UTF-8
test: $(TEST_DEPS)
$(Q) for t in $(TESTS); do \
$$t || exit 1; \ However on a board it fails to run |
I should also still try to make the test fail to see how the error is handled. |
I don't think we should override the user's locale system. Only obscure distributions do not configure utf-8 locales for users... Thus the build system is IMO not the right place. Murdock is a different story. I think the build workers actually do configure utf-8, but on the RPi worker node, this doesn't happen. We could either set that up in the RPi systemd unit file, or just in |
I wanted to overwrite it only for If not overwritten, then we should add as requirement that the system running the tests is configured to use |
From local testing, it looks like it should be configured in the Currently the locale in the container is
By doing a local test inspired from #11220 it fails in the current
The test fails due to the encoding errors.
When adding
|
+1, will PR a fix. |
I added a PR to try re-enabling these tests #12246 |
Description
Tests using
utf-8
characters fails in murdocknative
but work my developer machine.For the boards tests, it looks like they work correctly on the nodes but the report is not described as an
utf-8
document so show invalid output in the reports by default.Related to #9095 (comment)
Steps to reproduce the issue
Enable the given tests in CI and check the output.
Expected results
native
correctly.utf-8
characters by default on boards.Actual results
utf-8
fail withUnicodeEncodeError: 'ascii' codec can't encode characters in position
for nativeutf-8
.Versions
This is murdock specific so not RIOT.
The text was updated successfully, but these errors were encountered: