IRC channel logs


back to list of logs

<rekado>why does redirect to
<rekado>I think the browser on is better for our purposes because it includes more channels.
<civodul>it does that when it times out
<civodul>IOW, that indicates something’s wrong
<civodul>ACTION looks
<civodul>problem is bayfront is building lots of things, which often makes it damn slow
<civodul>not sure what happened
<civodul>there were signs of life yesterday at 11PM
<civodul>anyway, restarted it now :-/
<rekado>FYI: I’m testing the changes to the CRAN/Bioc channel scripts; they should now remove excessively large packages.
<rekado>the build queue on doesn’t seem to move forward
<rekado>sorry about filling up all these machines
<rekado>maybe we should build guix-cran/bioc on instead…?
<civodul>that’s ok, we just need to make sure we don’t consume 20GiB in 6h
<civodul>that’s quickly going to be a problem on ci.guix as well
<civodul>if you think this is now fix, i can run gc on workers and see how far it goes
<civodul>perhaps we’ll have to purge old builds from the queue too
<civodul>actually workers are active right now:
<civodul>but yeah, there’s about 8k queued builds, so it’ll take a while
<civodul>(assuming none of them exhausts worker storage too quickly)
<civodul>(besides, i told IT i wouldn’t mind getting more second-hand servers from them :-))
<rekado>it should be fixed in the scripts, but I need to use the scripts to update guix-bioc first (to remove the offending packages)
<rekado>it’s still running
<rekado>urgh, awful: the script caused a deletion of *all* packages in guix-bioc
<rekado>little bug somewhere
<civodul>oops :-)
<civodul>we don’t have to reduce the load on the build farm *that* much