[CI] Increase resource allocation for operational metrics cronjob #524
+3
−3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
boomanaiden154
approved these changes
Jul 25, 2025
Contributor
boomanaiden154
left a comment
boomanaiden154
left a comment
There was a problem hiding this comment.
LGTM.
I looked at least at the US central cluster yesterday and we had 2GB free on all three service nodes, so I this should be fine from a capacity perspective.
vvereschaka
pushed a commit
to vvereschaka/llvm-zorg
that referenced
this pull request
Sep 25, 2025
…vm#524) The cronjob for scraping llvm-project commit data consistently fails due to running out of memory. `git clone https://github.com/llvm/llvm-project.git` consistently uses around 1.5 GiB of RAM, which is well above both the request and limit currently set for the cronjob. Thus, the job is repeatedly killed more memory than is allocated. Increasing the resource allocation should get this cronjob running as intended.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The cronjob for scraping llvm-project commit data consistently fails due to running out of memory.
git clone https://github.com/llvm/llvm-project.gitconsistently uses around 1.5 GiB of RAM, which is well above both the request and limit currently set for the cronjob. Thus, the job is repeatedly killed more memory than is allocated.Increasing the resource allocation should get this cronjob running as intended.