apteryks

> I guess pahole could add a check for it and either skip the code or redefine the enum, but there's no easy define to check for this so frankly...

> We'll get a fix for this out in 5.45. Thanks for the reports, everyone! For the record, I'm still seeing this behavior. I do not use seahorse (the GNOME...

I have a similar report, from Guix System: ``` =========================== short test summary info ============================ FAILED tests/test_circular_imports.py::test_no_warnings[aiohttp._websocket] FAILED tests/test_circular_imports.py::test_no_warnings[aiohttp._helpers] - s... FAILED tests/test_circular_imports.py::test_no_warnings[aiohttp._http_writer] FAILED tests/test_circular_imports.py::test_no_warnings[aiohttp._http_parser] FAILED tests/test_client_request.py::test_default_loop[pyloop] - DeprecationW... FAILED...

Hm, I tried testing this with GNU Guix and got stuck in Python dependency hell upgrades; it'll have to wait, sorry.

I confirm these no longer fail, thanks.

Passing `--noconftest` to pytest in turns breaks all the tests using the compressed file fixture, e.g.: ``` ==================================== ERRORS ==================================== ___________ ERROR at setup of test_roundtrip_compression_with_files ____________ file /tmp/guix-build-python-brotlicffi-1.1.0.0.drv-0/brotlicffi-1.1.0.0/test/test_simple_compression.py, line...

Ah, thanks for pointing that out. Indeed, `recursive?` defauts to #f in Guix, as that's typically used to fetch 3rd party libraries and we generally prefer to package these separately.

And it looks like in the meantime someone figured it out in Guix :-). See https://codeberg.org/guix/guix/commit/ebf301e359188a32bfd130a40f6d89b48389b7cd.

I'm also seeing this issue on GNU Guix when attempting to use something like: ``` qemu-system-x86_64 [...] -m 5g -display spice-app -device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x6 -chardev spicevmc,name=vdagent,id=vdagent -device virtserialport,nr=1,bus=virtio-serial0.0,chardev=vdagent,name=com.redhat.spice.0 ``` QEMU is...

Applying the above patch ([3660acfcbaaca9c66dca5ef09205bd7c1d70b98c](https://gitlab.freedesktop.org/spice/linux/vd_agent/-/commit/3660acfcbaaca9c66dca5ef09205bd7c1d70b98c)) to spice-vdagent seems to have gotten rid of the error messages, thank you! If I make sure to use `-device qxl-vga` with QEMU, the resolution...