Haskell Foundation DevOps Weekly Log, 2022-08-05

Hello again!

During week 12, I identified new types of spurious CI failures and kicked over a rock that may have been hiding a few more. There were a few ops-y tasks and a little community involvement as well.

Done recently

  • Handled a minor GitLab incident involving abuse of the service
  • Looked into signal 9 errors
    • I suspected the OOM-killer, but free memory reporting looks ok
      • Though the reporting is only at a 15-second granularity
    • By themselves, it’s hard to say what’s going on with these errors, but see below
  • Looked at other errors
  • Alerted to problems with CI on bgamari/ghcs-nix
  • Commented on a few discussions on various proposals floating around. Generally I try to stay neutral and uninvolved, so I should probably scale that back. I think it’s an important way to avoid burnout (since I already work on supporting the community full-time). But community involvement is also important!

Coming up

  • Try to ensure jobs are not running out of memory
  • See if I can positively identify spurious errors out of the patterns of segfaults and missing output I’m seeing

Also in “Coming up”, the dates were confirmed for my absence: 18.8–25.9. I will delay next week’s log until Wednesday 17.8 so I can wrap up everything at once.

That’s all, have a nice weekend!

-Bryan
aka chreekat

4 Likes