You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/10/10 11:13:20 UTC
[GitHub] [airflow] Taragolis opened a new pull request, #26967: Increase pytest execution timeout for Dask test backfill integration
Taragolis opened a new pull request, #26967:
URL: https://github.com/apache/airflow/pull/26967
Seems like https://github.com/apache/airflow/pull/26831 a bit broke main tests for Dask Executor.
```
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
msg = 'Timeout >60.0s', pytrace = True
@_with_exception(Failed)
def fail(msg: str = "", pytrace: bool = True) -> "NoReturn":
"""Explicitly fail an executing test with the given message.
:param str msg:
The message to show the user as reason for the failure.
:param bool pytrace:
If False, msg represents the full failure information and no
python traceback will be reported.
"""
__tracebackhide__ = True
> raise Failed(msg=msg, pytrace=pytrace)
E Failed: Timeout >60.0s
/usr/local/lib/python3.8/site-packages/_pytest/outcomes.py:153: Failed
During handling of the above exception, another exception occurred:
```
**Testing API Always CLI Core Integration Other Providers WWW**. Test Core executed with this setup:
```
setup timeout: 60.0s, execution timeout: 60.0s, teardown timeout: 60.0s
```
I’m not sure but seems like test cases within `unittests.TestCase` ignore pytest timeouts.
I just grab randomly couple of previous success run before change base class for tests cases and time to time it ran more than 60s without interruption.
```
109.13s call tests/executors/test_dask_executor.py::TestDaskExecutor::test_backfill_integration
77.16s call tests/executors/test_dask_executor.py::TestDaskExecutor::test_backfill_integration
59.75s call tests/executors/test_dask_executor.py::TestDaskExecutor::test_backfill_integration
112.74s call tests/executors/test_dask_executor.py::TestDaskExecutor::test_backfill_integration
63.18s call tests/executors/test_dask_executor.py::TestDaskExecutor::test_backfill_integration
```
BTW, seems like it is second slowest test in Test Core after after `TestStringifiedDAGs::test_serialization`
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk merged pull request #26967: Increase pytest execution timeout for Dask test backfill integration
Posted by GitBox <gi...@apache.org>.
potiuk merged PR #26967:
URL: https://github.com/apache/airflow/pull/26967
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] Taragolis commented on pull request #26967: Increase pytest execution timeout for Dask test backfill integration
Posted by GitBox <gi...@apache.org>.
Taragolis commented on PR #26967:
URL: https://github.com/apache/airflow/pull/26967#issuecomment-1273156122
cc: @uranusjr @potiuk
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org