From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Subject: [Buildroot] Analysis of runtime test failures
Date: Sun, 20 Feb 2022 17:02:22 +0100 [thread overview]
Message-ID: <20220220170222.06d88b45@windsurf> (raw)
Hello,
Six of our runtime tests are failing, so I went ahead and quickly look
at the error messages. Here is my summary:
=== tests.package.test_ipython.TestIPythonPy3 ===
https://gitlab.com/buildroot.org/buildroot/-/jobs/2088684091
Error is:
# ipython -c 'import math; math.floor(12.3)'
-sh: ipython: not found
=== tests.package.test_python_pyyaml.TestPythonPy3Pyyaml ===
https://gitlab.com/buildroot.org/buildroot/-/jobs/2088684091
Error is:
# python sample_python_pyyaml_dec.py
Traceback (most recent call last):
File "/root/sample_python_pyyaml_dec.py", line 5, in <module>
data = yaml.load(serialized)
TypeError: load() missing 1 required positional argument: 'Loader'
=== tests.package.test_luasyslog.TestLuaLuasyslog ===
https://gitlab.com/buildroot.org/buildroot/-/jobs/2088683903
Error is:
>>> luasyslog 2.2.0 Building
PATH="/builds/buildroot.org/buildroot/test-output/TestLuaLuasyslog/host/bin:/builds/buildroot.org/buildroot/test-output/TestLuaLuasyslog/host/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" /usr/bin/make -j33 -C /builds/buildroot.org/buildroot/test-output/TestLuaLuasyslog/build/luasyslog-2.2.0/
/usr/bin/make all-am
CC lsyslog.lo
CC compat-5.3.lo
In file included from lsyslog.c:11:
compat-5.3.h:402:4: error: #error "unsupported Lua version (i.e. not Lua 5.1, 5.2, or 5.3)"
# error "unsupported Lua version (i.e. not Lua 5.1, 5.2, or 5.3)"
^~~~~
In file included from compat-5.3.c:7:
compat-5.3.h:402:4: error: #error "unsupported Lua version (i.e. not Lua 5.1, 5.2, or 5.3)"
# error "unsupported Lua version (i.e. not Lua 5.1, 5.2, or 5.3)"
^~~~~
make[3]: *** [Makefile:710: lsyslog.lo] Error 1
=== tests.package.test_lxc.TestLxc ===
https://gitlab.com/buildroot.org/buildroot/-/jobs/2088683908
Error is:
# lxc-start -l trace -n lxc_iperf3 -o /tmp/lxc.log -L /tmp/lxc.console.log
lxc-start: lxc_iperf3: lxccontainer.c: wait_on_daemonized_start: 868 Received container state "ABORTING" instead of "RUNNING"
lxc-start: lxc_iperf3: tools/lxc_start.c: main: 306 The container failed to start
lxc-start: lxc_iperf3: tools/lxc_start.c: main: 309 To get more details, run the container in foreground mode
lxc-start: lxc_iperf3: tools/lxc_start.c: main: 312 Additional information can be obtained by setting the --logfile and --logpriority options
# echo $?
=== tests.package.test_rust.TestRustBin ===
https://gitlab.com/buildroot.org/buildroot/-/pipelines/470182758/failures
Build issue while building the example Rust application:
/usr/bin/ld: /tmp/tmpdggplkto-br2-testing-rust/hello-world/target/armv7-unknown-linux-gnueabihf/debug/deps/hello_world-e03f93fef10567c3.1ajq7aud2z9fxhe5.rcgu.o: error adding symbols: file in wrong format
collect2: error: ld returned 1 exit status
Could
https://patchwork.ozlabs.org/project/buildroot/patch/20220217230638.98748-1-moritz@h6t.eu/
be related ?
=== tests.package.test_rust.TestRust ===
Same error as above.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-02-20 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-20 16:02 Thomas Petazzoni via buildroot [this message]
2022-02-20 16:25 ` [Buildroot] Analysis of runtime test failures Romain Naour
2022-02-20 19:35 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220220170222.06d88b45@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.