daroga0002 opened a new pull request, #1983:
URL: https://github.com/apache/apisix-ingress-controller/pull/1983

   <!-- Please answer these questions before submitting a pull request -->
   
   ### Type of change:
   
   <!-- Please delete options that are not relevant. -->
   
   <!-- Select all the options from below that matches the type your PR best -->
   
   - [ ] Bugfix
   - [ ] New feature provided
   - [ ] Improve performance
   - [ ] Backport patches
   - [ ] Documentation
   - [ ] Refactor
   - [ ] Chore
   - [x] CI/CD or Tests
   
   ### What this PR does / why we need it:
   
   This is solving issue with hardcoded version of Ginkgo module. There is 
strict dependency between tests in go using ginkgo package and local Ginkgo 
binary used for those tests. Currently after each update in dependencies CI 
start failing with log:
   
   ```sh
   Ginkgo detected a version mismatch between the Ginkgo CLI and the version of 
Ginkgo imported by your packages:
     Ginkgo CLI Version:
       2.12.0
     Mismatched package versions found:
       2.12.1 used by e2e
   
     Ginkgo will continue to attempt to run but you may see errors (including 
flag
     parsing errors) and should either update your go.mod or your version of the
     Ginkgo CLI to match.
   
     To install the matching version of the CLI run
       go install github.com/onsi/ginkgo/v2/ginkgo
     from a path that contains a go.mod file.  Alternatively you can use
       go run github.com/onsi/ginkgo/v2/ginkgo
     from a path that contains a go.mod file to invoke the matching version of 
the
     Ginkgo CLI.
   
     If you are attempting to test multiple packages that each have a different
     version of the Ginkgo library with a single Ginkgo CLI that is currently
     unsupported.
   ```
   
   This PR should fetch a correct version from e2e tests go.mod file and then 
install it in correct version.
   
   ### Pre-submission checklist:
   
   <!--
   Please follow the requirements:
   1. Use Draft if the PR is not ready to be reviewed
   2. Test is required for the feat/fix PR, unless you have a good reason
   3. Doc is required for the feat PR
   4. Use a new commit to resolve review instead of `push -f`
   5. Use "request review" to notify the reviewer once you have resolved the 
review
   -->
   
   - [ ] Did you explain what problem does this PR solve? Or what new features 
have been added?
   - [ ] Have you added corresponding test cases?
   - [ ] Have you modified the corresponding document?
   - [ ] Is this PR backward compatible? **If it is not backward compatible, 
please discuss on the [mailing 
list](https://github.com/apache/apisix-ingress-controller#community) first**
   


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