#2 potential culprits: my changeset PR or

1 messages · Page 1 of 1 (latest)

latent sequoia
#

First run seems ok, but it ended with 13 of 16G used of RAM, and 3G on swap

#

Second run just started and took all the rest in a very short amount of time

#

My test is to run dagger call go lint --limit=1 (so from the PR above to have the --limit flag)

modern terrace
latent sequoia
#

yes, it doesn't matter