Hi Yanfei, Thanks for your information, I will take a look~
Best Rui Fan On Wed, Feb 8, 2023 at 11:36 AM Yanfei Lei <fredia...@gmail.com> wrote: > Hi Rui, > > In this case I would search the log for `Run Kubernetes test` in > > https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_apis/build/builds/45813/logs/216 > first, and then we can see: > > 2023-02-07T10:25:38.6193935Z X Exiting due to RUNTIME_ENABLE: > Temporary Error: sudo /usr/local/bin/crictl version: exit status 1 > 2023-02-07T10:25:38.6195335Z stdout: > 2023-02-07T10:25:38.6195720Z > 2023-02-07T10:25:38.6196446Z stderr: > 2023-02-07T10:25:38.6198596Z time="2023-02-07T10:25:38Z" level=fatal > msg="unable to determine runtime API version: rpc error: code = > Unavailable desc = connection error: desc = \"transport: Error while > dialing dial unix /var/run/cri-dockerd.sock: connect: connection > refused\"" > ... > > I'm guessing there is a problem when starting minikube, something like > https://issues.apache.org/jira/browse/FLINK-28269. > > Rui Fan <1996fan...@gmail.com> 于2023年2月8日周三 11:25写道: > > > > Hi Yun, > > > > Thanks for your quick reply. > > > > I have downloaded, however it just has the watchdog log. > > The flink-logs directory is empty. > > > > Best > > Rui Fan > > > > > > On Wed, Feb 8, 2023 at 11:09 AM Yun Tang <myas...@live.com> wrote: > > > > > Hi Rui, > > > > > > The detailed logs of flink e2e CI can be found in the published > artifacts > > > [1] which start with "logs-ci-e2e_1_ci". > > > > > > [1] > > > > https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=45813&view=artifacts&pathAsName=false&type=publishedArtifacts > > > > > > Best > > > Yun Tang > > > ________________________________ > > > From: Rui Fan <fan...@apache.org> > > > Sent: Wednesday, February 8, 2023 10:46 > > > To: dev <dev@flink.apache.org> > > > Subject: How to find the root cause of e2e ci failure? > > > > > > Hi masters: > > > > > > When test_ci core or connect fails, we can see which test failed. > > > But I don't know how to find the root cause of e2e ci failure?[1] > > > And I just see: > > > > > > `'Run Kubernetes test' failed after 4 minutes and 19 seconds! Test > exited > > > with exit code 1`. > > > > > > Could any master share some experiences? Thank you so much. > > > > > > [1] > > > > > > > https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=45813&view=results > > > > > > Best > > > Rui Fan > > > > > > > -- > Best, > Yanfei >