Add nightly throughput stress #1173
Open
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
THardy98
force-pushed
the
add-nightly-throughput-stress-workflow
branch
from
5826aa5 to
3c55e17
Compare
Sushisource
reviewed
Oct 20, 2025
Comment on lines
17
to
21
| timeout: | ||
| description: 'Scenario timeout (should always be 30m more than duration)' | ||
| required: false | ||
| default: '6h30m' | ||
| type: string |
There was a problem hiding this comment.
If it should always be that we could just calculate it
There was a problem hiding this comment.
It doesn't necessarily need to be this, it just needs to be greater than the duration, but it's a good default.
I'll fix the comment.
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.
What was changed
Added a nightly workflow to run Omes throughput stress scenario.
Runs throughput stress with a minimum throughput expectation.
Uploads worker logs artifacts and sends a Slack notification on failure.
Why?
Provides basic smoke/stress testing, with a base benchmark throughput expectation.