neverCase commented on pull request #845:
URL: 
https://github.com/apache/apisix-ingress-controller/pull/845#issuecomment-1022076000


   ci error below:
   ```sh
   • Failure [70.707 seconds]
   ApisixRoute Testing
   
/home/runner/work/apisix-ingress-controller/apisix-ingress-controller/test/e2e/ingress/resourcepushing.go:28
     service is referenced by two ApisixRoutes [It]
     
/home/runner/work/apisix-ingress-controller/apisix-ingress-controller/test/e2e/ingress/resourcepushing.go:502
   
     
        Error Trace:    resourcepushing.go:607
                                                runner.go:113
                                                runner.go:64
                                                it_node.go:26
                                                spec.go:215
                                                spec.go:138
                                                spec_runner.go:200
                                                spec_runner.go:170
                                                spec_runner.go:66
                                                suite.go:79
                                                ginkgo_dsl.go:238
                                                ginkgo_dsl.go:213
                                                e2e_test.go:26
        Error:          "[%!s(*v1.Upstream=&{{45e6c8e6 
ingress-apisix-e2e-tests-default-428202328_httpbin-service-e2e-test_80 Created 
by apisix-ingress-controller, DO NOT modify it manually 
map[managed-by:apisix-ingress-controller]} roundrobin vars  <nil> [{10.244.2.32 
80 100}] http <nil> <nil> <nil>})]" should have 0 item(s), but has 1
        Test:           ApisixRoute Testing service is referenced by two 
ApisixRoutes
   ```
   maybe it need to re-run once again. @tao12345666333 


-- 
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]


Reply via email to