-
-
Notifications
You must be signed in to change notification settings - Fork 6.2k
Improve FetchTask reliability / performance #35960
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
base: main
Are you sure you want to change the base?
Improve FetchTask reliability / performance #35960
Conversation
|
|
||
| workflowJob, err := job.ParseJob() | ||
| if err != nil { | ||
| return nil, false, fmt.Errorf("load job %d: %w", job.ID, err) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This ends in a fetch loop such job should be updated to failed?
|
I conclude, this test is a denial of service for sqlite of this change: Not even a single job reports anything EDIT 16 Nov 2025 Updating the sqlite database took 30minutes, for 25 parallel runners that do not upload logs. Maybe need to run this test against different databases, maybe they work better. Also need to run this against the default branch. Mysql and Mariadb also support locking rows of the pending jobs, that maybe could optimize them. Otherwise Gitea Actions should be coordinated rate limited between gitea and runner to maintain responsiveness This test took > 10 minutes on a m4 pro macbook |
Fixes #33492
Feedback welcome and maybe need to link another existing issue.