Skip to content

don't need to specify =true in commandline flags anymore #358

don't need to specify =true in commandline flags anymore

don't need to specify =true in commandline flags anymore #358

Triggered via push December 2, 2024 05:58
Status Success
Total duration 4m 37s
Artifacts

sanity.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

10 errors
build
use BeforeEach() to assign variable vWhen
build
use BeforeEach() to assign variable vContext
build
ginkgo-linter: wrong comparison assertion. Consider using `Expect(p1).To(BeIdenticalTo(p2))` instead
build
ginkgo-linter: comparing a pointer to a value will always fail. Consider using `Expect(p1).ToNot(HaveValue(Equal(6)))` instead
build
ginkgo-linter: comparing a pointer to a value will always fail. Consider using `Expect(p1).ToNot(HaveValue(Equal(6)))` instead
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