[
https://issues.apache.org/jira/browse/FLINK-31180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-31180:
-----------------------------------
Labels: stale-minor starter test-stability (was: starter test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Fail early when installing minikube and check whether we can retry
> ------------------------------------------------------------------
>
> Key: FLINK-31180
> URL: https://issues.apache.org/jira/browse/FLINK-31180
> Project: Flink
> Issue Type: Improvement
> Components: Test Infrastructure
> Affects Versions: 1.17.0, 1.15.3, 1.16.1
> Reporter: Matthias Pohl
> Priority: Minor
> Labels: stale-minor, starter, test-stability
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=46367&view=logs&j=bea52777-eaf8-5663-8482-18fbc3630e81&t=b2642e3a-5b86-574d-4c8a-f7e2842bfb14&l=4726
> We experienced a build failure where Minikube couldn't be installed due to
> some network issues. Two things which we could do here:
> * check whether we can add a retry loop (maybe also to other resource)
> * fail early if CI didn't manage to install the binaries
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
