Summary: | dev-libs/ell-0.30 : [TEST] FAIL: unit/test-uuid | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Lars Wendler (Polynomial-C) (RETIRED) <polynomial-c> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bkohler |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge-info.txt
dev-libs:ell-0.30:20200328-062242.log emerge-history.txt environment etc.portage.tbz2 logs.tbz2 temp.tbz2 .config |
Description
Toralf Förster
![]() there is still a similar issue at unstable amd64 tinderbox image 17.1_desktop_gnome_systemd-libressl_test-20200327-211737 (see bug 657352) Created attachment 626502 [details]
emerge-info.txt
Created attachment 626504 [details]
dev-libs:ell-0.30:20200328-062242.log
Created attachment 626506 [details]
emerge-history.txt
Created attachment 626508 [details]
environment
Created attachment 626510 [details]
etc.portage.tbz2
Created attachment 626512 [details]
logs.tbz2
Created attachment 626514 [details]
temp.tbz2
I closed the other bug under the assumption that the test failure was due to a few missing kernel config options but I have added checks and your build.log doesn't show any missing options found. I will look into this again/deeper. Currently I'm unable to reproduce the failure anywhere. Is your tinderbox's current kernel .config available somewhere? Created attachment 626550 [details]
.config
kernel config (make default FWIW)
I see now. It's (lack of) CRYPTO_USER_API_HASH which is making this test fail. I'm adding a check for that, and also add a dep on dbus (found out that's required for these tests) And NOW I can see that we're already testing for this, but only in pkg_pretend so it doesn't show in your build.log. I think I will need the check to happen in pkg_setup as well. I reworked the ebuild slightly so that the linux-info exported pkg_setup phase handles this by default. The (failed) check should now show up in your build.log. You still cannot pass all tests with your kernel config as-is though. |