You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One unit test is flaky and from time to time takes too much time to run, causing CI to terminate the process: bin/pytest tests/test_service_cli.py::test_shutdown_called_on_shutdown_signal
The text was updated successfully, but these errors were encountered:
artem-shelkovnikov
changed the title
Flaky test: tests/test_service_cli.py::test_shutdown_called_on_shutdown_signal[Signals.SIGTERM]
Flaky test: tests/test_service_cli.py::test_shutdown_called_on_shutdown_signal[Signals.SIGINT]
May 13, 2024
Tried looking into it and it's really weird, feels like it's an interrupt that happens in a wrong moment.
Testing it a bit locally showed that the test does not interrupt because some services (in my case it was job cleanup service) did not exit.
I think it happens because SIGINT/SIGTERM happens in between service startup - e.g. Job Scheduling/Job Execution Services has just started, next Job Cleanup Service will attempt to start, but interrupt happens before and service just starts.
☝️ This info is just a theory, I was unable to prove or discard it.
One unit test is flaky and from time to time takes too much time to run, causing CI to terminate the process:
bin/pytest tests/test_service_cli.py::test_shutdown_called_on_shutdown_signal
The text was updated successfully, but these errors were encountered: