- 
                Notifications
    You must be signed in to change notification settings 
- Fork 140
Add nightly throughput stress #1173
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
Conversation
5826aa5    to
    3c55e17      
    Compare
  
    | timeout: | ||
| description: 'Scenario timeout (should always be 30m more than duration)' | ||
| required: false | ||
| default: '6h30m' | ||
| type: string | 
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.
If it should always be that we could just calculate it
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.
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.
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.