Paul Murphy
Paul Murphy
Is there more context to be found about what test is suspected of hanging, and what the timeout is? I am rebuilding the container images to include lsof.
Hrm, I wonder if this is timing out more frequently because the jobs are not running on a tmpfs. The only tmpfs I have mounted to the containers is /workdir...
I've also changed the docker configuration to mount /home/swarming as a tmpfs.
The latest batch of failures is the same issue as #65725. I only adjusted the RAM limits on the ppc64le LUCI containers. Looking through the logs, the ppc64-power10 LUCI containers...
The net/http failures should be attributed to #67382, notably they have not been mentioned on the other issue. Reclosing this issue.
I inspected [ppc64-power10 failure ](https://ci.chromium.org/b/8746487826012416609) directly before this message. It shows many failures, but not those which caused the timeout. Inspecting the go testing log, I see the timing out...
The spur of power10/ppc64 failures in early may is almost certainly an OOM for the reason I noted in #60148.
I think we can ignore these for now. I've been fine tuning the LUCI builders. They should all be 4 cores / 10G RAM now. The old buildlets are limited...
This flake stills falls under my previous comment. The failure can be ignored.
To use the libdfp headers, you need to include them from the installed path. They live inside their own directory. For example, if using libdfp via the fedora package, you...