https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: dev-dotnet/fable-4.9.0 fails tests (hang). Discovered on: amd64 (internal ref: ci) Info about the issue: https://wiki.gentoo.org/wiki/Project:Tinderbox/Common_Issues_Helper#CF0016
Created attachment 883756 [details] build.log build log and emerge --info
for last fable bug (which actually was a test failure in disguise) I had checked out this combination also - what I want to say is that I could not reproduce this hang on my machine. Could be a tinderbox bug.
(In reply to Maciej Barć from comment #2) > for last fable bug (which actually was a test failure in disguise) I had > checked out this combination also - what I want to say is that I could not > reproduce this hang on my machine. Could be a tinderbox bug. Thanks for the update, but 'Could be a tinderbox bug' means little especially for CI that is a pretty standard system, just ~amd64. Does this test make use of MAKEOPTS? If yes it could be the high number of parallel jobs that I have here.
(In reply to Agostino Sarubbo from comment #3) > Does this test make use of MAKEOPTS? If yes it could be the high number of > parallel jobs that I have here. It does, the call is right in the log... It could be true that this hangs the process. > -maxCpuCount:61
version 4.9.0 is long gone