apache / apisix

The Cloud-Native API Gateway
https://apisix.apache.org/blog/
Apache License 2.0
14.32k stars 2.49k forks source link

request help: ci faied due to lack of memory #6076

Closed zhixiongdu027 closed 2 years ago

zhixiongdu027 commented 2 years ago

Issue description

4880

In this Pr, I added some code to set up a k8s cluster. common.sh

but it looks like it fails with no clear error message.

someone can help! TKS ~_~

Environment

tzssangglass commented 2 years ago

@tao12345666333 @leslie-tsang PLAT

tao12345666333 commented 2 years ago

FYI

https://github.com/apache/apisix-ingress-controller/blob/de522437bd3db3dc3e8d8f33c92f322de67531b8/.github/workflows/e2e-test-ci.yml#L74-L90

zhixiongdu027 commented 2 years ago

@tao12345666333 @tzssangglass Hi: Sorry, I set a wrong issues title.

I don't actually want to know how the script or job to build a k8s cluster is defined.

What I want to know is why this CI fails, and there is no prompt message. ubuntu-18.04, linux_openresty (ubuntu-18.04, linux_openresty_1_17)

In fact, using kind to create a k8s cluster has been successful. (ubuntu-18.04, linux_openresty_1_17)

and using minikube to create a k8s cluster has been failed . chaos-test

leslie-tsang commented 2 years ago

and using minikube to create a k8s cluster has been failed . chaos-test

Hello there, chaos test failed due to dependencies relying on deprecated git protocol, plz check #6073 out.

In fact, using kind to create a k8s cluster has been successful. (ubuntu-18.04, linux_openresty_1_17)

I suspect there is not enough memory to launch both basic CI env and k8s service. more detail in #5200

zhixiongdu027 commented 2 years ago

I suspect there is not enough memory to launch both basic CI env and k8s service. more detail in #5200

if so, What can I do . Creating a new cluster is a necessary condition for test k8s discovery module .

tokers commented 2 years ago

I suspect there is not enough memory to launch both basic CI env and k8s service. more detail in #5200

if so, What can I do . Creating a new cluster is a necessary condition for test k8s discovery module .

Try to run your test suites in a separated github action workflow, so that you don't have to launch a couple of components which are not related to your cases.

zhixiongdu027 commented 2 years ago

I got your point. Maybe it can work ,but wiil be always failed in other ci

leslie-tsang commented 2 years ago

Maybe it can work ,but wiil be always failed in other ci

Try to run your test suites in a separated github action workflow, so that you don't have to launch a couple of components which are not related to your cases.

It should work. 🤣

zhixiongdu027 commented 2 years ago

@leslie-tsang I mean even if I can create a new ci just for testing kubernetes.t But kubernetes.t will still run in centos-ci , build-ci and will eventually fail

zhixiongdu027 commented 2 years ago

maybe we can split test cases into two or more ci ?