Paul Murphy

I think gopherbot reopened this against failure @archanaravindar already observed and committed a fix for yesterday. @archanaravindar does this fix need [backported](https://github.com/golang/go/wiki/MinorReleases) to go1.19?

I have not had much time to digest this yet. Speaking for my PPC64 work, I have no existing plans to rewrite our assembler. Adding ISA 3.1 support (particularly for...

I changed `/home/swarming` on the LUCI builders to a tmpfs mount on 2/13, that seemed to consistently fail during this test as it went over the 8G RAM limits of...

Looking at the VM, it did trigger an OOM on a container. The syslog is claiming 7.5G of that is "file" usage. Is there any way to make LUCI more...

I didn't realize the ppc64 LUCI builder also needed a bump too. It is bumped to 10g. If this doesn't crash again in the next week, this issue can be...

Poking around at the idle ppc64le builders, there is a folder "/home/swarming/.cache/gopls" which is consuming between 2.5G and 3.3G on each instance. That's a problem. Is it possible to update...

For reference, this is what has accrued on linux-ppc64le-power8--05 since the last container reboot: ``` 832K .cache/gopls/013c47f3 259M .cache/gopls/01a3ac08 136M .cache/gopls/0634c015 88M .cache/gopls/0d9f1c10 64M .cache/gopls/1045283d 258M .cache/gopls/159d94d7 142M .cache/gopls/17fdaa63 144M...

I've set `GOPLSCACHE=/home/swarming/.swarming/w` via the container image on all ppc64x luci builders while waiting for a more generic fix.

I set up some of the new builders to use 8G instead of 10G memory limits, which can OOM rangegen tests. That has since been resolved for the last week...

I wonder if LUCI needs to set `GO_TEST_TIMEOUT_SCALE=2` for ppc64{,le}? I don't think I see that set in the logs. The POWER8 builders can be particularly slow. I think the...