[erlang-questions] Processes get stuck in prim_inet:recv0

[Loïc Hoguin]

Hello,

I have a container that's most likely subtly broken (most recent Arch 
Linux on a slightly older Arch Linux) and I'm not sure why. It only 
started happening after I rebuilt it a few days ago, the difference 
between before/after is more recent packages on the container and little 
else.

It has a symptom that's consistent across all Erlang versions I'm 
testing (most recent patch releases of 19.*, 20.*, 21.0-rc1 and 20.3.6 
compiled in native mode, and all are compiled on the same system with 
kerl): the process gets stuck in prim_inet:recv0 and it makes CT fail 
with a timetrap timeout[1].

It happens a few times per test runs, at a rate of maybe 2 or 3 times 
per hour.

Have you seen this before? If yes how do I fix this? Is there any useful 
data I can get that would help?

Thanks,

[1] 
https://builds.ninenines.eu/logs/cowboy-prs/79/archlinux/ct_run.ct_cowboy@archlinux0.2018-05-24_15.25.14/ninenines.cowboy-prs.rfc7230_SUITE.logs/run.2018-05-24_15.33.18/rfc7230_suite.timeout_after_request_line.2283.html

-- 
Loïc Hoguin
https://ninenines.eu