ci: gnu parallel set --memfree 100M

[ggilmore]

See golangci/golangci-lint#994

It seems like golang-ci lint uses a fair amount of memory. Running that in parallel with yarn steps might be causing memory issues / flakes. Downgrading golang-ci doens't seem to help.

I discovered a new flag for gnu parallel, --memfree $SIZE that prevents queuing new tasks if < $SIZE memory is free and will kill and restart tasks if < $SIZE/2 memory remains. Let's see if this fixes things.

see https://www.gnu.org/software/parallel/man.html

---

Believed to be the cause of flakes like https://buildkite.com/sourcegraph/sourcegraph/builds/58560#a827d10a-4c85-4822-bc1d-f3e3f9571792

[uwedeportivo]

i approved since i'm in the middle of releasing and need CI to be unclogged :-)

[keegancsmith]

I recently enabled the unused staticcheck again. It likely has increased the memory usage to much. We can just disable it, the value it provides continuously is likely not worth the resource cost.

[dominikh]

I recently enabled the unused staticcheck again. It likely has increased the memory usage to much. We can just disable it, the value it provides continuously is likely not worth the resource cost.

Note also that I am working on reducing memory usage in a future release (although to benefit from it, one would have to use the staticcheck tool, not golangci-lint.)

[keegancsmith]

I recently enabled the unused staticcheck again. It likely has increased the memory usage to much. We can just disable it, the value it provides continuously is likely not worth the resource cost.

Note also that I am working on reducing memory usage in a future release (although to benefit from it, one would have to use the staticcheck tool, not golangci-lint.)

Yeah I'm not actually sure when we switched to golanglint-ci, we used to directly use staticcheck. I'd be happy to switch to that again :) Also thank you so much for investigating reducing memory usage, its a tough problem to solve!