Sindweller commented on pull request #670:
URL: 
https://github.com/apache/apisix-ingress-controller/pull/670#issuecomment-915884001


   Should have resolved the error in unit-test. It's due to the lack of cluster 
`metricCollector`.
   But I need help to solve the e2e-test failed errors, like:
   `Error:              Expected nil, but got: &errors.errorString{s:"timed out 
waiting for the condition"}`
   ```
   • Failure in Spec Setup (BeforeEach) [86.687 seconds]
   rewrite annotations
   
/Users/sindweller/apisix-ingress-controller/test/e2e/annotations/rewrite.go:28
     enable in ingress networking/v1beta1 [BeforeEach]
     
/Users/sindweller/apisix-ingress-controller/test/e2e/annotations/rewrite.go:62
   
     
        Error Trace:    scaffold.go:325
                                                runner.go:113
                                                runner.go:64
                                                setup_nodes.go:15
                                                spec.go:193
                                                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:          Expected nil, but got: &errors.errorString{s:"timed out 
waiting for the condition"}
        Test:           rewrite annotations enable in ingress networking/v1beta1
        Messages:       waiting for ingress apisix controller ready
   ```
   It seems my changes may not affect these files and cause the error.


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