AlinsRan opened a new issue, #1077:
URL: https://github.com/apache/apisix-ingress-controller/issues/1077
### Issue description
Running e2e on the local machine or CI is particularly unstable and
occasionally failed.
It is stable for a single use case, but it is mutually exclusive for
multiple use cases. In a multi-threaded environment, it often fails.
**proposal: It is recommended to use single thread to solve or refactor the
e2e.**
### Environment
- your apisix-ingress-controller version (output of
apisix-ingress-controller version --long):
- your Kubernetes cluster version (output of kubectl version):
- if you run apisix-ingress-controller in Bare-metal environment, also show
your OS version (uname -a):
### Minimal test code / Steps to reproduce
1. The multiple use cases, concurrent running is not supported, they are
mutually exclusive.
* `cd test/e2e && ginkgo --focus='suite-ingress' --nodes=10`
2. It is stable for single use cases.
* `cd test/e2e && ginkgo --focus='all resources will be watched'`
### Actual result
Failed.
### Error log
None.
### Expected result
_No response_
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
