[
https://issues.apache.org/jira/browse/FLINK-21636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chesnay Schepler updated FLINK-21636:
-------------------------------------
Description:
We should setup a timeout that is applied automatically to all tests. This can
be even something like 10 minutes.
Right now, a single test not terminating eats 4 hours of CI time, and with
Azure's inability to cancel running stages can hurt productivity quite a bit.
Implementation wise, we can just add this to the {{TestLogger}} class.
{code}
@Rule
public Timeout globalTimeout = Timeout.minutes(10);
{code}
was:
We should setup a timeout that is applied automatically to all tests. This can
be even something like 10 minutes.
Right now, a single test not terminating eats 4 hours of CI time, and with
Azure's inability to cancel running stages can hurt productivity quite a bit.
> Setup a global timeout for all tests
> ------------------------------------
>
> Key: FLINK-21636
> URL: https://issues.apache.org/jira/browse/FLINK-21636
> Project: Flink
> Issue Type: Improvement
> Components: Test Infrastructure
> Reporter: Chesnay Schepler
> Priority: Major
> Fix For: 1.13.0
>
>
> We should setup a timeout that is applied automatically to all tests. This
> can be even something like 10 minutes.
> Right now, a single test not terminating eats 4 hours of CI time, and with
> Azure's inability to cancel running stages can hurt productivity quite a bit.
> Implementation wise, we can just add this to the {{TestLogger}} class.
> {code}
> @Rule
> public Timeout globalTimeout = Timeout.minutes(10);
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
