Hi,
On Sun, Sep 15, 2024 at 06:08:21PM -0400, John David Anglin wrote:
> Source: feedbackd
> Version: 0.4.1-1
> Severity: normal
> Tags: ftbfs
>
> Dear Maintainer,
>
> Package fails to build:
> 8/9 fbd-dev-led FAIL 0.19s killed by signal 6 SIGABRT
> >>> GSETTINGS_SCHEMA_DIR=/<<PKGBUILDDIR>>/_build/data
> >>> PYTHONDONTWRITEBYTECODE=yes G_TEST_BUILDDIR=/<<PKGBUILDDIR>>/_build/tests
> >>> MALLOC_CHECK_=2 XDG_CONFIG_DIRS=/<<PKGBUILDDIR>>/tests
> >>> G_DEBUG=gc-friendly,fatal-warnings MALLOC_PERTURB_=36
> >>> XDG_DATA_DIRS=/<<PKGBUILDDIR>>/tests/data/xdg-data
> >>> XDG_CONFIG_HOME=/<<PKGBUILDDIR>>/tests/data/user-config
> >>> G_TEST_SRCDIR=/<<PKGBUILDDIR>>/tests
> >>> UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
> >>> GSETTINGS_BACKEND=memory MESON_TEST_ITERATION=1
> >>> ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1
> >>> MSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
> >>> umockdev-wrapper /<<PKGBUILDDIR>>/_build/tests/test-fbd-dev-led
> ――――――――――――――――――――――――――――――――――――― ✀ ―――――――――――――――――――――――――――――――――――――
> stdout:
> TAP version 13
> # random seed: R02S460381b4ca5b4369d3bb9b84ad5810b4
> 1..5
> # Start of feedbackd tests
> # Start of fbd tests
> # Start of dev tests
> # Start of led tests
> # DEBUG: umockdev.vala:127: Created udev test bed /tmp/umockdev.HYGUS2
> # DEBUG: umockdev.vala:1307: parsing device description for
> /devices/LNXSYSTM:00/LNXSYBUS:00/PURI4543:00/leds/blue:status
> # DEBUG: umockdev.vala:1385: creating device
> /devices/LNXSYSTM:00/LNXSYBUS:00/PURI4543:00/leds/blue:status (subsystem leds)
> # DEBUG: umockdev.vala:1307: parsing device description for
> /devices/LNXSYSTM:00/LNXSYBUS:00/PURI4543:00
> # DEBUG: umockdev.vala:1385: creating device
> /devices/LNXSYSTM:00/LNXSYBUS:00/PURI4543:00 (subsystem acpi)
> # DEBUG: umockdev.vala:1307: parsing device description for
> /devices/LNXSYSTM:00/LNXSYBUS:00
> # DEBUG: umockdev.vala:1385: creating device /devices/LNXSYSTM:00/LNXSYBUS:00
> (subsystem acpi)
> # DEBUG: umockdev.vala:1307: parsing device description for
> /devices/LNXSYSTM:00
> # DEBUG: umockdev.vala:1385: creating device /devices/LNXSYSTM:00 (subsystem
> acpi)
> # DEBUG: umockdev.vala:1565: enable: failed to remove /disabled flag,
> ignoring: No such file or directory
> not ok /feedbackd/fbd/dev/led/simple -
> ERROR:../tests/test-fbd-dev-led.c:31:test_fbd_dev_led_simple: assertion
> failed (g_list_length (leds) == 1): (0 == 1)
> Bail out!
> stderr:
> **
> ERROR:../tests/test-fbd-dev-led.c:31:test_fbd_dev_led_simple: assertion
> failed (g_list_length (leds) == 1): (0 == 1)
> ――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
>
> Full log is here:
> https://buildd.debian.org/status/fetch.php?pkg=feedbackd&arch=hppa&ver=0.4.1-1&stamp=1724073857&raw=0
>
> Running under gdb, we have:
> (gdb) break test-fbd-dev-led.c:31
> Breakpoint 1 at 0x410088f0: file ../tests/test-fbd-dev-led.c, line 31.
> (gdb) r
> The program being debugged has been started already.
> Start it from the beginning? (y or n) y
> Starting program:
> /home/dave/debian/feedbackd/feedbackd-0.4.1/_build/tests/test-fbd-dev-led
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/hppa-linux-gnu/libthread_db.so.1".
> TAP version 14
> # random seed: R02Sde8102d5a1d3016362c45737e203cb85
> 1..5
> # Start of feedbackd tests
> # Start of fbd tests
> # Start of dev tests
> # Start of led tests
> [New Thread 0xf653e040 (LWP 4882)]
> # DEBUG: umockdev.vala:127: Created udev test bed /tmp/umockdev.ZJT5T2
> # DEBUG: umockdev.vala:1307: parsing device description for
> /devices/LNXSYSTM:00/LNXSYBUS:00/PURI4543:00/leds/blue:status
> [New Thread 0xf5d3d040 (LWP 4884)]
> # DEBUG: umockdev.vala:1385: creating device
> /devices/LNXSYSTM:00/LNXSYBUS:00/PURI4543:00/leds/blue:status (subsystem leds)
> [New Thread 0xf553c040 (LWP 4885)]
> # DEBUG: umockdev.vala:1307: parsing device description for
> /devices/LNXSYSTM:00/LNXSYBUS:00/PURI4543:00
> # DEBUG: umockdev.vala:1385: creating device
> /devices/LNXSYSTM:00/LNXSYBUS:00/PURI4543:00 (subsystem acpi)
> # DEBUG: umockdev.vala:1307: parsing device description for
> /devices/LNXSYSTM:00/LNXSYBUS:00
> # DEBUG: umockdev.vala:1385: creating device /devices/LNXSYSTM:00/LNXSYBUS:00
> (subsystem acpi)
> # DEBUG: umockdev.vala:1307: parsing device description for
> /devices/LNXSYSTM:00
> # DEBUG: umockdev.vala:1385: creating device /devices/LNXSYSTM:00 (subsystem
> acpi)
> # DEBUG: umockdev.vala:1565: enable: failed to remove /disabled flag,
> ignoring: No such file or directory
>
> Thread 1 "test-fbd-dev-le" hit Breakpoint 1, test_fbd_dev_led_simple (
> fixture=<optimized out>, unused=<optimized out>)
> at ../tests/test-fbd-dev-led.c:31
> 31 g_assert_cmpint (g_list_length (leds), ==, 1);
> (gdb) p leds
> $1 = (GUdevDevice_listautoptr) 0x0
>
> Same error occurs on alpha.
Hmmmm...The LED tests require LD_PRELOAD'ing umockdev to work which
seems to be happening but the result of
`g_udev_client_query_by_subsystem` is empty. This isn't even feedbackd
related code, just plain gudev + udevmock so I wonder what could be
different on alpha / hppa?
Tried to reproduce on panama.debian.net but can't get a sid schroot with
build-deps there:
$ dd-schroot-cmd -c sid_hppa-dchroot-8ecf7517-dd36-44d5-a4a2-a97d01dcb458
apt-get update
/usr/local/bin/dd-schroot-cmd:59: SyntaxWarning: invalid escape sequence '\.'
if re.search('^\.|~$|[^0-9a-zA-Z_.~-]', session):
File "/usr/local/bin/dd-schroot-cmd", line 124
except OSError, e:
In case someone wants to investigate: This runs the single failing test:
umockdev-run -- _build/tests/test-fbd-dev-led
Cheers,
-- Guido
>
> Regards,
> Dave Anglin
>
> -- System Information:
> Debian Release: trixie/sid
> APT prefers unreleased
> APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable')
> Architecture: hppa (parisc64)
>
> Kernel: Linux 6.10.10-dirty (SMP w/4 CPU threads)
> Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_CA:en
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> _______________________________________________
> Debian-on-mobile-maintainers mailing list
> debian-on-mobile-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-on-mobile-maintainers
