Skip to content

Fix false positive when asserting an error pointer #371

Fix false positive when asserting an error pointer

Fix false positive when asserting an error pointer #371

Triggered via push December 11, 2024 08:07
Status Success
Total duration 4m 40s
Artifacts

sanity.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
build
ginkgo-linter: the MatchError matcher used to assert a non error type ("example")
build
ginkgo-linter: MatchError first parameter (42) must be error, string, GomegaMatcher or func(error)bool are allowed
build
ginkgo-linter: missing function description as second parameter of MatchError
build
ginkgo-linter: The second parameter of MatchError must be the function description (string)
build
ginkgo-linter: redundant MatchError arguments; consider removing them
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
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636