Aleks-Daniel Jakimenko-Aleksejev

Buildable is up and running, it'll take a few days to rebuild the builds with the older GLIBC. Otherwise, everything looks good now! I haven't deleted the wrong builds yet,...

I have removed all builds that required a newer GLIBC. That was about 2000 builds. They'll be rebuilt automatically. Currently, there is a new build per roughly 6 minutes, so...

> Because it has fewer restrictions than camelia Actually, not really. Camelia didn't have any proper restrictions. All it did was use the RESTRICTED misfeature in rakudo, which as far...

See also: https://github.com/perl6/whateverable/issues/25

This and https://github.com/Raku/whateverable/issues/374 are the same issue, I think. Due to progress in https://github.com/Raku/whateverable/issues/388, all bots are now dockerized, and they have a very limited amount of write access to...

I'm not sure if this is needed. Each bot has its own `/tmp` directory, so bots don't compete for the builds. It is possible, however, that multiple people will try...

Actually, because of https://github.com/facebook/zstd/issues/3062, it's not a win-win situation. For 20 rakudo builds the results are like this: | Command | Compression time | File size | Decompression time |...

There's a [`time-left` sub](https://github.com/perl6/whateverable/blob/0357ee557cfc6b23d97fd13fca1123e98bdc0cce/lib/Whateverable/Bits.pm6#L92-L104), maybe it can be extended/repurposed to talk about dates in the past? Yes, I think “X years, etc.” is a better format. Also if it happens...

Any updates? :) I'd love to merge this.

> \ No, .moarvm files won't be identical since the compiler's id contains the SHA of the full source code Bummer. So there's no relatively easy way of detecting that....