insomnes commented on issue #47939: URL: https://github.com/apache/airflow/issues/47939#issuecomment-2742772138
> Actually, I haven't run the test_kubernetes_pod_operator_active_deadline_seconds locally before. Could the long duration of the test be related to cmds=["sh", "-c", "echo 'hello world' && sleep 60"], the command we use to test KubernetesPodOperator? If so, maybe shortening the sleep time while still simulating a long-running job would be sufficient. As I understand the `active_deadline_secods` setting mechanism it sets the maximum running time for the pod (including `PENDING` state). So this test is checking cluster will fail the pod if it's running any longer. This way test duration depends on the timer set. But we also may lower the `sleep` value for speeding up the failure route of the case if it happens. >Not sure if running the test only once would be ideal. It's a great idea to check with the test author! I didn't think about it, thanks! I am sorry for the off-topic on this issue. I only wanted to pre-validate my ideas before trying the implementation. I hope I didn't bother you all much. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
