Cannot start CI jobs

[mscdex]

The benchmark-node-micro-benchmarks job does nothing after submitting a job. I've already tried re-logging in, but that did not seem to help. I was able to start one of these jobs just the other day, so I'm not sure what's going on.

[targos]

I've renamed the issue as I think the problem exists for all jobs. I cannot start any job anymore.

[rvagg]

Disk full on ci.nodejs.org, caused by disk full on our backup server which does the pruning. i haven't dealt with the latter but I've invoked the pruner manually (/root/backup_scripts/remove_old.sh ci.nodejs.org for those with access). I've done a system update and restart of the server so it should be happy again. But this problem won't go away until we deal with the full backup server. We'll be back at max disk until that's resolved and working normally. So we'd better leave this issue open.

[aduh95]

Not sure if this is related, but the @nodejs-github-bot doesn't comment anymore on the PR when a CI is started. I've seen that on nodejs/node#36679 and nodejs/node#29412.

[rvagg]

^ can someone confirm whether the bot is still broken or not and needs some attention from someone who has a clue?

[mmarchini]

Not the case, there's a comment from 21 hours ago. Also, more recent from the last CI run: nodejs/node#36648

[aduh95]

I think this can be closed now, the issue on CI has been resolved AFAICT.