LUA_PATH="./?.lua;;" \ LUA_CPATH="./?.so;;" \ /usr/bin/dbus-run-session /usr/bin/lua5.1 tests/test.lua (process:174): Lgi-WARNING **: 15:49:46.973: Error raised while calling 'lgi.cbk (number): Regress': attempt to call a number value (process:174): Lgi-WARNING **: 15:49:46.973: Error raised while calling 'lgi.cbk (string): Regress': attempt to call a string value ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_plasma-j4_test-20220330-230006 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-11.2.1 * clang/llvm (if any): clang version 14.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/14/bin /usr/lib/llvm/14 14.0.0 Python 3.9.12 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby27 (with Rubygems) [3] ruby31 (with Rubygems) * Available Rust versions: [1] rust-1.59.0 * The following VMs are available for generation-2: *) Eclipse Temurin JDK 11.0.14_p9 [openjdk-bin-11] 2) Eclipse Temurin JDK 8.322_p06 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 [2] openjdk-bin-11 system-vm The Glorious Glasgow Haskell Compilation System, version 8.10.4 php cli: [1] php7.4 [2] php8.0 * [3] php8.1 HEAD of ::gentoo commit 18d4dd73ed8866ece214f2f752ae92d74b780d80 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Tue Apr 5 11:49:36 2022 +0000 2022-04-05 11:49:33 UTC emerge -qpvO dev-lua/lgi [ebuild N ] dev-lua/lgi-0.9.2-r100 USE="test -examples" LUA_TARGETS="lua5-1 -lua5-3 -lua5-4 -luajit"
Created attachment 768892 [details] emerge-info.txt
Created attachment 768893 [details] dev-lua:lgi-0.9.2-r100:20220405-134939.log
Created attachment 768894 [details] emerge-history.txt.bz2
Created attachment 768895 [details] environment
Created attachment 768896 [details] etc.portage.tar.bz2
Created attachment 768897 [details] temp.tar.bz2
Created attachment 768898 [details] tests.tar.bz2
*** Bug 840532 has been marked as a duplicate of this bug. ***