| Summary: | x11-libs/gdk-pixbuf-2.42.10 fails tests: asyncio.exceptions.CancelledError, asyncio.exceptions.TimeoutError | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jonathan Lovelace <kingjon3377> |
| Component: | Current packages | Assignee: | Mike Gilbert <floppym> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | CC: | williamh |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://github.com/mesonbuild/meson/issues/10752 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
x11-libs:gdk-pixbuf-2.42.10:20221110-223307.log
emerge-info.txt |
||
Created attachment 830709 [details]
emerge-info.txt
I'm not sure I understand what this means or how it works, but I *do* know you're not the only one to see this, because it was also submitted as https://github.com/mesonbuild/meson/issues/10752 Unfortunately I'm not deeply familiar with that part of the Meson codebase so I never investigated closely. Obviously, it's situation-dependent whether it will error out at all... |
Created attachment 830707 [details] x11-libs:gdk-pixbuf-2.42.10:20221110-223307.log =x11-libs/gdk-pixbuf-2.42.10 fails its test phase for me. After showing seven "OK" tests in the standard(?) Meson test-runner format, the log shows two screens of multiple Python stack traces for asyncio.exceptions.CancelledError and asyncio.exceptions.TimeoutError, followed by a summary of 7 "Ok" and "0" failures, and then "ERROR: Unhandled python exception This is a Meson bug and should be reported!"