Codeberg-e.V./requests
55
63
Fork
You've already forked requests
10

[CI] Increase Resources #644

Closed
opened 2025年03月17日 11:11:32 +01:00 by malik · 3 comments

Projects

Expected Resource Usage

medium

I would also like the following users to be added

No response

Additional Information

I was granted minimal resources in the past but run into timout issues.
I am not building the packages and modules for all platforms, only evaluating their nix definitions

Other Work

No response

Statement

  • I have placed a LICENSE file in my repository. (Or equivalent, such as COPYING or a LICENSES folder)
  • I understand that Codeberg's CI might not always be available or stable, despite best efforts.
  • I understand that I can use the feedback repository to share feedback or report problems.
### Projects - [Datalad-Nix](https://codeberg.org/malik/datalad-nix) ### Expected Resource Usage medium ### I would also like the following users to be added _No response_ ### Additional Information I was granted minimal resources in the past but run into [timout issues](https://ci.codeberg.org/repos/14322/pipeline/62/55). I am not building the packages and modules for all platforms, only evaluating their nix definitions ### Other Work _No response_ ### Statement - [x] I have placed a LICENSE file in my repository. (Or equivalent, such as `COPYING` or a [LICENSES folder](https://reuse.software)) - [x] I understand that Codeberg's CI might not always be available or stable, despite best efforts. - [x] I understand that I can use the [feedback repository](https://codeberg.org/Codeberg-CI/feedback) to share feedback or report problems.

I belive timeout settings are set on an instance-level, rather than based on this questionnaire. I think @pat-s could offer more insight into this, or point us to someone who can?

I belive timeout settings are set on an instance-level, rather than based on this questionnaire. I think @pat-s could offer more insight into this, or point us to someone who can?
Member
Copy link

Resources and timeouts are two different things.
I cannot see a timeout issue in the linked build.
Besides, we can't control timeouts on the user level.

Your resource need it not medium or large but on the excessive scale. You run > 20 jobs on each ljll/PR which run 40-1h each (!).
Also in the process itself the bandwidth use is very high due to many downloads.

Please drastically reduce/rethink your CI workflows, resource use at this level falls into the "wasted resources" category.

If you don't agree and absolutely want to continue these builds, please provide your own runner (undocumented still right now).

Resources and timeouts are two different things. I cannot see a timeout issue in the linked build. Besides, we can't control timeouts on the user level. Your resource need it not medium or large but on the excessive scale. You run > 20 jobs on each ljll/PR which run 40-1h each (!). Also in the process itself the bandwidth use is very high due to many downloads. Please drastically reduce/rethink your CI workflows, resource use at this level falls into the "wasted resources" category. If you don't agree and absolutely want to continue these builds, please provide your own runner (undocumented still right now).

I'm considering this request as denied with the explicit ask to reduce the currently used resources ASAP. Closing.

I'm considering this request as **denied** with the explicit ask to reduce the currently used resources ASAP. Closing.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg-e.V./requests#644
Reference in a new issue
Codeberg-e.V./requests
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?