-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Excessive use of builds.sr.ht #17479
Comments
Agreed. We should do this ASAP. |
This means to delete
How to accomplish that? |
I've now disabled the webhooks which were triggered by pull requests. Now it should be commits-only. (I'll monitor new pull requests to see if that's really the case, to be sure.) |
Yep, and merge anything it would have done into the other manifest.
Head to https://dispatch.sr.ht and disable the appropriate task. |
Thanks @narimiran |
Thanks, done. |
Ooops... |
@ddevault See #17480: no sr.ht BSD CIs anymore.
I had no information about this being an old well-known problem. Hopefully, this change should bring our usage way down. If there's a similar problem in the future, please ping me too (together with @Araq). |
Thanks for the speedy response! |
Hi folks. I've spoken with ~araq about this several times, but it continues to be a problem. Nim makes excessive use of builds.sr.ht, far more than almost any other project does. You have submitted 275 builds today alone, totaling over 200 hours of build time. For context, a similar level of usage on CircleCI would cost you almost $75 per day. This is causing disruptions for other users.
Please reduce your OpenBSD builds to just one manifest, and do whatever testing you need to do in serial rather than in parallel. Please also disable your builds for pull requests and only build commits - your contributors are too often pushing and repushing tens of commits to each pull request, most of which don't need to be built.
I've been trying to address this issue with the Nim project for several months now. If a timely resolution is not found, I will be terminating service for your project.
The text was updated successfully, but these errors were encountered: