fhuzero commented on pull request #406: URL: https://github.com/apache/apisix-ingress-controller/pull/406#issuecomment-829008252
> > > @fhuzero Hi! Does this PR ready to review? > > > > > > Sad that the code failed to pass some ci checks so probably it's not ready to be merged. When I run test cases in Minikube on my local machine, though the test for retrieving server info succeed most times, it fails randomly because of some errors such as `waiting for apisix ready`, `no etcd`, `TLS handshake timeout`, etc. These errors will recover later without intervention. It would be great if someone can give me guidance on how to avoid the random failure. > > We recommend you to use [Kind](https://kind.sigs.k8s.io/) as the Cluster to run e2e test suites, also, you may need to push these images to minikube before you start to run them, too long time for pulling images might lead to some timeout assertions failed. Thanks for your recommendation! I did follow three steps listed in [Quick Start](https://github.com/apache/apisix-ingress-controller/tree/master/test/e2e#quick-start) in Apisix ingress controller e2e test suites Readme file. When running test for the first time, I created a cluster by Kind and all test cases passed. After that, I used `E2E_SKIP_BUILD=1` to skip the first two steps. Then the aforementioned errors occurred randomly. Please let me know if I overlooked anything. -- 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. For queries about this service, please contact Infrastructure at: [email protected]
