[AIRFLOW-6460] Reduce timeout in pytest#7051
Conversation
|
@mik-laj is 90s too short? I consistently hit this in travis: |
This reverts commit bf3fa1f.
|
Yep @tooptoop4 -> I reverted it and also added #7064 to show errors immediately when they happen (that is actually the problem this timeout decrease tried to address). |
…pache#7062) This reverts commit bf3fa1f.
Hello
I am not sure, but I suspect that when the test is marked as flaky, the time without writing to the console exceed the Travis limits, because maximum time is performed repeatedly, and in the meantime, nothing is written on the screen. Unfortunately, after 10 minutes Travis stops the job.
I suggest drastically reducing this timeout . This will also prevent the introduction of a test that would slow down our CI. I chose the value of 90 seconds based on the list of slowest tests (available below). The slowest test takes 50s, so 90 seconds is a sensible value. Travis CI can sometimes be overloaded, so 50 seconds can be dangerous.
Link to JIRA issue: https://issues.apache.org/jira/browse/AIRFLOW-6460
[AIRFLOW-NNNN], where AIRFLOW-NNNN = JIRA ID*(*) For document-only changes, no JIRA issue is needed. Commit message starts
[AIRFLOW-XXXX].In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.
Read the Pull Request Guidelines for more information.