You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the report. While I cannot exclude a bug in libmodulemd, I suspect the cause is in glib. Do glib tests pass for you on the same system? Could you give me more details about the system? E.g. what portage profile (17.1 or 23.0) is used. I'd like to reproduce it locally, but I need to know which stage to use. Is it http://ftp.linux.cz/pub/linux/gentoo/releases/amd64/autobuilds/current-stage3-amd64-musl-llvm/?
Activity
ppisar commentedon Mar 27, 2024
Thanks for the report. While I cannot exclude a bug in libmodulemd, I suspect the cause is in glib. Do glib tests pass for you on the same system? Could you give me more details about the system? E.g. what portage profile (17.1 or 23.0) is used. I'd like to reproduce it locally, but I need to know which stage to use. Is it http://ftp.linux.cz/pub/linux/gentoo/releases/amd64/autobuilds/current-stage3-amd64-musl-llvm/?
Kangie commentedon Mar 28, 2024
That is a good question; I unpacked this chroot before the 23.0 profiles were stablised - a quick look says that it's a 17.0 profile:
You may be right about the root cause of these failures being glib:
I'll see if I can find any info in our bug tracker about these failures, maybe they've already been reported upstream?
Edit: We have a Gentoo bug, which is linked to issues or merge requests for pretty much all of those issues. https://bugs.gentoo.org/864789