You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This apparently happens often at the end of month, and I think this is bad, because we may easily have no CI feeback for FreeBSD for days (or even weeks, if the amount of pushes increases). So unless somebody would pay for a compute limit increase, maybe we should stop running CirrusCI for every push, but instead have nightly runs, and a way to manually trigger the workflow in cases where it seems relevant. I don't know if that's possible, though.
We discussed this when Cirrus stopped their unlimited free tier. The main "issue" with testing nightly is that Cirrus doesn't have a built-in way to send e-mails on error. So, we'd have to implement that (or Slack notifications) ourselves. Since we thought just moving the ASAN build to GitHub was enough, we did that.
Description
This apparently happens often at the end of month, and I think this is bad, because we may easily have no CI feeback for FreeBSD for days (or even weeks, if the amount of pushes increases). So unless somebody would pay for a compute limit increase, maybe we should stop running CirrusCI for every push, but instead have nightly runs, and a way to manually trigger the workflow in cases where it seems relevant. I don't know if that's possible, though.
cc @devnexen
The text was updated successfully, but these errors were encountered: