Skip to content

Fix bug: ginkgolinter ignores the Error() method #354

Fix bug: ginkgolinter ignores the Error() method

Fix bug: ginkgolinter ignores the Error() method #354

Triggered via push November 11, 2024 15:09
Status Success
Total duration 4m 17s
Artifacts

sanity.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
build
ginkgo-linter: "Expect": missing assertion method. Expected "To()", "ToNot()" or "NotTo()"
build
ginkgo-linter: "Eventually": missing assertion method. Expected "Should()" or "ShouldNot()"
build
ginkgo-linter: multiple issues: timeout defined more than once; polling defined more than once
build
ginkgo-linter: multiple issues: only use time.Duration for timeout and polling in Eventually() or Consistently(); only use time.Duration for timeout and polling in Eventually() or Consistently(). Consider using `Consistently(func() bool { return true }, time.Second*10, time.Second).Should(BeTrue())` instead
build
ginkgo-linter: timeout must not be shorter than the polling interval
build
ginkgo-linter: Success matcher only support a single error value, or function with Gomega as its first parameter
build
ginkgo-linter: wrong error assertion. Consider using `Eventually(func() error { return err }).Should(Succeed())` instead
build
ginkgo-linter: Success matcher does not support multiple values
build
ginkgo-linter: Success matcher only support a single error value, or function with Gomega as its first parameter
build
ginkgo-linter: wrong error assertion. Consider using `Eventually(func() error { return err }).Should(Succeed())` instead
build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/