jason810496 commented on issue #47939:
URL: https://github.com/apache/airflow/issues/47939#issuecomment-2742676366

   > What do you think about tuning them? Would it be reasonable regarding the 
test suite speed up and k8s tests stability?  
   I think we can achieve minor gains on such checks by introducing a delay of 
5 seconds and lowering the startup probe's period and timeout because they are 
quite high for the local kind cluster environment. And these timeouts could be 
configured the same way via helm.  
   
   Sure, that sounds good to me for system tests, as they can be configured via 
Helm options. Feel free to create another PR to fine-tune it!  
   
   > These two tests are the longest in the pod operator test suite.  
   
   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.  
   
   > even only once  
   
   Not sure if running the test only once would be ideal.  
   cc @amoghrajesh
   


-- 
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]

Reply via email to