Draft
Conversation
|
Skipping CI for Draft Pull Request. |
dcaravel
added
generate-dumps-on-pr
Contributor
Author
|
Well.. that didn't seem to have any impact on throughput. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
generate-db-dumpstep in.github/workflows/ci.yamlhas been taking > 1h10mWhen this job takes a long time dependent jobs start timing out. For example, konflux jobs poll for 1hr for an image before giving up and OSCI jobs also hit the current 2h total runtime limit (considering increasing this)
This PR attempts to tune the temp postgres DB to focus on performance vs. durability on crash (we don't care about crash here, CI would fail regardless)