This is an auto-filled bug because sys-apps/util-linux fails tests. The issue was originally discovered on amd64, but it may be reproducible on other arches as well. If you think that a different summary clarifies the issue better, feel free to change it. Attached build log and emerge --info.
Created attachment 635282 [details] build.log.bz2 build log and emerge --info
> misc: mountpoint: [01] default ... FAILED (misc/mountpoint-default) > misc: mountpoint ... FAILED (1 from 3 sub-tests)
I cannot reproduce this.
Please attach files matching the pattern below. /var/tmp/portage/sys-apps/util-linux-2.35.1-r2/work/util-linux-2.35.1-abi_x86_64.amd64/tests/output/misc/mountpoint*
(In reply to Mike Gilbert from comment #4) > Please attach files matching the pattern below. > > /var/tmp/portage/sys-apps/util-linux-2.35.1-r2/work/util-linux-2.35.1- > abi_x86_64.amd64/tests/output/misc/mountpoint* I have: $ file mountpoint* mountpoint: empty mountpoint-default: ASCII text mountpoint-default.err: empty mountpoint.err: empty mountpoint-mutually-exclusive: ASCII text mountpoint-mutually-exclusive.err: ASCII text mountpoint-nofollow: ASCII text mountpoint-nofollow.err: empty I will attach only non empty files.
Created attachment 635492 [details] mountpoint-default mountpoint-default
Created attachment 635494 [details] mountpoint-mutually-exclusive mountpoint-mutually-exclusive
Created attachment 635496 [details] mountpoint-mutually-exclusive.err mountpoint-mutually-exclusive.err
Created attachment 635498 [details] mountpoint-nofollow mountpoint-nofollow
ago: I cannot reproduce this on infra's amd64 or remaining x86 boxes.
I can reproduce this on arm64. misc: mountpoint: [01] default ... FAILED (misc/mountpoint-default) misc: mountpoint ... FAILED (1 from 3 sub-tests) # cat /var/tmp/portage/sys-apps/util-linux-2.35.1-r2/work/util-linux-2.35.1-.arm64/tests/output/misc/mountpoint* ./symlink-to-root is not a mountpoint 1 1 mountpoint: --devno and --nofollow are mutually exclusive ./symlink-to-root is not a mountpoint 1 ---- Using https://github.com/trofi/gentoo-chrootiez to enter the chroot which may be relevant somehow.
Does this test fail with the current stable version of util-linux?
(In reply to Mike Gilbert from comment #12) > Does this test fail with the current stable version of util-linux? No, can't seem to get it on =sys-apps/util-linux-2.33.2.