Replies

• 

  Veronica Olsen 🍂veronica@mastodon.online

  Oct 31, 2026, 1:31 PM

  @amethyst We had the additional fun result that since our VMs ground to a halt at 14:00, people moved to scheduled CI jobs instead, so then between 14 and 16 each day, no one could get a PR through because all the runners were queued up for the next 2h. 😅

  💬 0🔄 2⭐ 3
• 

  Joe Wdrchaos@sauropods.win

  Nov 1, 2026, 5:44 AM

  @amethyst @veronica @hzulla same here - active monitoring would create concurrent spikes in system load (which we don't archive over months) and thus in job runtime (which is kept for analysis) not really visible with the naked eye, but looking at the latter using resampling and fft made it really visible. We moved that part of the active monitoring to a later point in the script and selected a different start time in all calling offices...
  Yeah, obvious in hindsight.

  💬 0🔄 1⭐ 0