Skip to content
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.

Sign up for GitHub

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

Jump to bottom

GitHub action takes 30 minutes because of sequential execution #13

Closed
Stefterv opened this issue Nov 13, 2024 · 1 comment · Fixed by #14
Closed

GitHub action takes 30 minutes because of sequential execution #13

Stefterv opened this issue Nov 13, 2024 · 1 comment · Fixed by #14
Labels
bug Something isn't working

Comments

@Stefterv
Copy link
Collaborator

Describe the bug

The update script runs sequentially

Raph and I have disabled the action for now as it was eating into the build minutes for the Org. After the fix we can enable it again!

Steps to reproduce

Running the update action takes 30 minutes

Expected behavior

Running the update action should take as long as the longest request / timeout

Actual behavior

No response
@Stefterv Stefterv added the bug Something isn't working label Nov 13, 2024
@mingness
Copy link
Collaborator

I see, you'd rather do a number of hits in clusters, async, rather than one after the other.

@SableRaf SableRaf changed the title Describe the bug GitHub action takes 30 minutes because of sequential execution Nov 13, 2024
@Stefterv Stefterv mentioned this issue Dec 13, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Added multi-threading to the update script processing/processing-contributions
2 participants
@Stefterv @mingness