Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 906357 - dev-libs/concurrencykit-0.7.1-r1 fails tests (hang) (MUSL-SYSTEM)
Summary: dev-libs/concurrencykit-0.7.1-r1 fails tests (hang) (MUSL-SYSTEM)
Status: RESOLVED CANTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Conrad Kostecki
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-14 20:46 UTC by Agostino Sarubbo
Modified: 2023-07-31 08:14 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
build.log (build.log,240.33 KB, text/plain)
2023-05-14 20:46 UTC, Agostino Sarubbo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Agostino Sarubbo gentoo-dev 2023-05-14 20:46:38 UTC
https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: dev-libs/concurrencykit-0.7.1-r1 fails tests (hang) (MUSL-SYSTEM).
Discovered on: amd64 (internal ref: tinderbox_musl)

NOTE:
(MUSL-SYSTEM) in the summary means that bug was found on a machine that runs MUSL libc but this bug MAY or MAY NOT BE related to musl.
I had to kill the process.
Comment 1 Agostino Sarubbo gentoo-dev 2023-05-14 20:46:40 UTC
Created attachment 861700 [details]
build.log

build log and emerge --info
Comment 2 Conrad Kostecki gentoo-dev 2023-07-28 07:32:30 UTC
@ago: Please mask this package on your testbox. I am not able to do anything here. I also spoke to upstream, they don't have any idea.

Upstream and me are unable to reproduce locally.
Comment 3 Agostino Sarubbo gentoo-dev 2023-07-31 08:14:01 UTC
Hello Conrad,

I understand your concern, but I did another test.

I build a machine on Hetzner cloud with centos7, then:

 - yum install docker -y
 - systemctl start docker
 - docker run -it -d --privileged --name mymachine gentoo/stage3
 - docker exec -it mymachine /bin/bash

Then, in the container:
 - emerge --sync -q
 - FEATURES="test" emerge -v dev-libs/concurrencykit

And I can reproduce the issue.

Also I'd suggest upstream to be more verbose in the test, so we can understand where the failure is.

By attaching to the barrier_centralized pid with strace I get:

futex(0x7fb061de0990, FUTEX_WAIT_BITSET|FUTEX_CLOCK_REALTIME, 1549, NULL, FUTEX_BITSET_MATCH_ANY

Anyway I can reproduce the test hang in 100% of cases.