Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ginkgo v1.10.3 get error with go 1.13.5 in kata tests #634

Closed
teawater opened this issue Dec 19, 2019 · 2 comments
Closed

ginkgo v1.10.3 get error with go 1.13.5 in kata tests #634

teawater opened this issue Dec 19, 2019 · 2 comments

Comments

@teawater
Copy link

go version
go version go1.13.5 linux/amd64
go get github.com/kata-containers/tests
cd $GOPATH/src/github.com/kata-containers/tests
make ginkgo
./ginkgo -failFast -v -focus "" -skip "" functional/ -- -runtime=kata-runtime -timeout=120
flag provided but not defined: -test.timeout

Usage of /tmp/ginkgo293695841/functional.test:
  -ginkgo.debug
        If set, ginkgo will emit node output to files when running in parallel.
  -ginkgo.dryRun
        If set, ginkgo will walk the test hierarchy without actually running anything.  Best paired with -v.
  -ginkgo.failFast
        If set, ginkgo will stop running a test suite after a failure occurs.
  -ginkgo.failOnPending
        If set, ginkgo will mark the test suite as failed if any specs are pending.
  -ginkgo.flakeAttempts int
        Make up to this many attempts to run each spec. Please note that if any of the attempts succeed, the suite will not be failed. But any failures will still be recorded. (default 1)
  -ginkgo.focus string
        If set, ginkgo will only run specs that match this regular expression.
  -ginkgo.noColor
        If set, suppress color output in default reporter.
  -ginkgo.noisyPendings
        If set, default reporter will shout about pending tests. (default true)
  -ginkgo.noisySkippings
        If set, default reporter will shout about skipping tests. (default true)
  -ginkgo.parallel.node int
        This worker node's (one-indexed) node number.  For running specs in parallel. (default 1)
  -ginkgo.parallel.streamhost string
        The address for the server that the running nodes should stream data to.
  -ginkgo.parallel.synchost string
        The address for the server that will synchronize the running nodes.
  -ginkgo.parallel.total int
        The total number of worker nodes.  For running specs in parallel. (default 1)
  -ginkgo.progress
        If set, ginkgo will emit progress information as each spec runs to the GinkgoWriter.
  -ginkgo.randomizeAllSpecs
        If set, ginkgo will randomize all specs together.  By default, ginkgo only randomizes the top level Describe, Context and When groups.
  -ginkgo.regexScansFilePath
        If set, ginkgo regex matching also will look at the file path (code location).
  -ginkgo.reportFile string
        Override the default reporter output file path.
  -ginkgo.reportPassed
        If set, default reporter prints out captured output of passed tests.
  -ginkgo.seed int
        The seed used to randomize the spec suite. (default 1576720667)
  -ginkgo.skip string
        If set, ginkgo will only run specs that do not match this regular expression.
  -ginkgo.skipMeasurements
        If set, ginkgo will skip any measurement specs.
  -ginkgo.slowSpecThreshold float
        (in seconds) Specs that take longer to run than this threshold are flagged as slow by the default reporter. (default 5)
  -ginkgo.succinct
        If set, default reporter prints out a very succinct report
  -ginkgo.trace
        If set, default reporter prints out the full stack trace when a failure occurs
  -ginkgo.v
        If set, default reporter print out all specs as they begin.
  -runtime string
        Path of the desired Kata Runtime
  -timeout int
        Time limit in seconds for each test (default 5)

Ginkgo ran 1 suite in 992.444361ms
Test Suite Failed
@blgm
Copy link
Collaborator

blgm commented Dec 19, 2019

Hi @teawater, this looks to be quite similar to #602 which documents a breaking change in Go 1.13. What do you think? There is a suggested change which fixed a similar error for other users. Let us know whether or not that works for you.

@blgm
Copy link
Collaborator

blgm commented Jan 6, 2020

I'm going to close this issue as I think an answer has been provided. Please feel free to re-open it if the suggestion above does not resolve the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants