-
Notifications
You must be signed in to change notification settings - Fork 122
Add KillCaller feature to test server for CLI crash recovery testing #4146
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
base: main
Are you sure you want to change the base?
Add KillCaller feature to test server for CLI crash recovery testing #4146
Conversation
89e1011 to
3a3b6f5
Compare
|
@denik could you please review this pr |
debc6c8 to
bcc288c
Compare
bcc288c to
ba053c3
Compare
|
@denik can you please queue the integration tests |
|
@denik bump ^^ |
|
Commit: ba053c3
21 interesting tests: 18 KNOWN, 2 FAIL, 1 SKIP
Top 25 slowest tests (at least 2 minutes):
|
Signed-off-by: Varun Deep Saini <varun.23bcs10048@ms.sst.scaler.com>
|
@denik Had a few questions,
|
|
An authorized user can trigger integration tests manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
Closes: #4140
Changes
Add
KillCalleroption to test server that terminates the CLI process when specific endpoints are hit. This enables testing crash recovery scenarios likebundle deployinterrupted mid-execution.KillCallerspecifies how many times to kill before allowing normal responses, enabling retry/recovery testing.Why
Enables testing CLI crash recovery scenarios (e.g.,
bundle deployinterrupted mid-execution).Tests
Added
acceptance/selftest/kill_caller/tests.