On windows, the worker agent creates a service when running install-deadline-worker (without the --no-service argument). One responsibility of this service is to restart the worker agent process if it exits (e.g. a program crash).
We require automated end-to-end testing to ensure this functionality works as expected.
What was the solution? (How)
Add a test that verifies that when windows worker shuts down by a SIGKILL signal, the worker service restarts the process.
Also moved around the other test in this class, so that we do not have to create 2 workers in this class, rather than one.
What is the impact of this change?
Better code quality for the code that is responsible for restarting the worker.
How was this change tested?
source .e2e_windows_infra.sh
hatch run e2e-test
Was this change documented?
No
Is this a breaking change?
No
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
What was the problem/requirement? (What/Why)
On windows, the worker agent creates a service when running
install-deadline-worker
(without the--no-service
argument). One responsibility of this service is to restart the worker agent process if it exits (e.g. a program crash).We require automated end-to-end testing to ensure this functionality works as expected.
What was the solution? (How)
Add a test that verifies that when windows worker shuts down by a SIGKILL signal, the worker service restarts the process.
Also moved around the other test in this class, so that we do not have to create 2 workers in this class, rather than one.
What is the impact of this change?
Better code quality for the code that is responsible for restarting the worker.
How was this change tested?
Was this change documented?
No
Is this a breaking change?
No
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.