Dominik Picheta
Dominik Picheta
Do we need another CI for this? Can't we do it in travis?
To be honest, I wonder whether this should even be done every commit. It seems like it would be very flaky. We should have it run continuously every day or...
If we can get a list of packages that Nimble `master` fails on but where the last stable Nimble succeeds then that would be very high signal. But setting up...
It can give good signal, but I'd rather it not block PRs/commits which is why I think it should be run separately. Also, I would prefer if it didn't depend...
That could work but only if we can avoid noise in GitHub's UI.
We now have Github Actions, can we do it there?
To be honest, I'm still preferring a separate repo for this so that we can avoid delaying the CI status.
> For good reasons: https://research.swtch.com/version-sat This is a classic, if you haven't already then check out the "Alternatives?" section. Some of the suggestions may sound familiar.  Specifying a concrete...
Have you tried different GCs? Maybe `--gc:markAndSweep` or `--gc:orc`? For a simple HTML this definitely shouldn't happen (how much increase do you see?). For larger files I can see that...
Not sure what you mean? The Load More Threads button seems to take the same amount of time to load each time I click it.