You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/02/24 22:57:00 UTC

[jira] [Commented] (AIRFLOW-6906) Flaky test_kubernetes_executor.py

    [ https://issues.apache.org/jira/browse/AIRFLOW-6906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17043945#comment-17043945 ] 

ASF GitHub Bot commented on AIRFLOW-6906:
-----------------------------------------

potiuk commented on pull request #7525: [AIRFLOW-6906] Fix flaky tests in kubernetes tests
URL: https://github.com/apache/airflow/pull/7525
 
 
   
 
----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Flaky test_kubernetes_executor.py 
> ----------------------------------
>
>                 Key: AIRFLOW-6906
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-6906
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: ci
>    Affects Versions: 2.0.0
>            Reporter: Jarek Potiuk
>            Priority: Major
>
> Kubernetes executors are flaky - seems this is a race where (quite often) monitor_task gets 404 instead of "connection error" or success. It seems we should treat 404 same way as connection error as it indicates that the webserver is running but the task was not yet submitted to the DB



--
This message was sent by Atlassian Jira
(v8.3.4#803005)