Open twrightsman opened 3 days ago
The error look as if you'd be running the tests from a Godot binary in /usr/bin
, but they're only supported when ran "in place" in the Git repository.
ERROR: Cannot open CryptoKeyMbedTLS file '/usr/bin/../tests/data/crypto/in.key'.
That path should be /mnt/godot-build/godot3/bin/../tests/data/crypto/in.key
.
I know distro packagers tend to patch software to match distro requirements (I've been there myself on Mageia/Fedora), do you have any downstream patches that could impact this? Or are you maybe running the tests from the binary already installed in /usr/bin
or PATH
inadvertently?
If you can share the debian/
files, I'm familiar with the system and might be able to spot what's wrong.
Compiling on bookworm and running the tests does successfully produce a backtrace:
To get a proper backtrace you should compile with debug_symbols=yes
passed explicitly.
Sorry for the confusion! I did indeed run the Godot binaries from /usr/bin
instead of the command I wrote.
Copying the binaries into bin/
and running them on Debian unstable gives only a few failing tests for the editor (the release template passed all tests :tada:):
To get a proper backtrace you should compile with
debug_symbols=yes
passed explicitly.
Turning this option on seemed to try to compile everything, including things specified as builtin_*=no
, even with separate_debug_symbols=yes
. Is there a way to just generate debug symbols for the built code and rely on distro-provided debug symbols for the others?
If you are interested, the MR is here. The Debian GitLab instance is currently being upgraded so it may be offline when you try to visit.
For what it's worth, I added static_icu_data=no
to the build command but got the same test results.
Tested versions
System information
Godot v4.3.stable (17df8f24f) - Debian GNU/Linux 12 (bookworm) 12 - Wayland - GLES3 (Compatibility) - Mesa Intel(R) UHD Graphics 620 (KBL GT2) - Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (8 Threads)
Issue description
I am working to package 4.3-stable in Debian but have encountered a few unit test failures on both Debian stable/bookworm as well as bleeding-edge unstable (in a VM). Apologies if this is too many issues at once. I am happy to split this up further if that's easier! The logs are mostly identical, so here is the result from inside the unstable VM:
Compiling on bookworm and running the tests does successfully produce a backtrace:
On the unstable VM there is also
Illegal instruction
reported at the very end and on stable it instead showsAborted
.Steps to reproduce
For Debian stable/bookworm:
For unstable I just add
libembree-dev
and usebuiltin_embree=no
, as unstable has a recent enough libembree.Minimal reproduction project (MRP)
N/A