[jira] [Updated] (YUNIKORN-1249) Upgrade ginkgo from v1 to v2

["Manikandan R (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/YUNIKORN-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manikandan R updated YUNIKORN-1249:
-----------------------------------
    Summary: Upgrade ginkgo from v1 to v2  (was: ginkgov2 timeout issue)

> Upgrade ginkgo from v1 to v2
> ----------------------------
>
>                 Key: YUNIKORN-1249
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1249
>             Project: Apache YuniKorn
>          Issue Type: Sub-task
>          Components: test - e2e
>            Reporter: Manikandan R
>            Assignee: Manikandan R
>            Priority: Major
>              Labels: newbie
>
> I tried ginkgov2 to run e2e tests but it fails with following error:
> mani@mani-MBP16 e2e % /Users/mani/go/bin/ginkgo -r -v timeout=5m recovery_and_restart -- -yk-namespace "default" -kube-config /User/mani/.kube/config
> flag provided but not defined: -ginkgo.timeout
> Usage of /Users/mani/codebase/yunikorn/incubator-yunikorn-k8shim/test/e2e/recovery_and_restart/recovery_and_restart.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 value
>     	If set, ginkgo will only run specs that match this regular expression. Can be specified multiple times, values are ORed.
>   -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 1655795912)
>   -ginkgo.skip value
>     	If set, ginkgo will only run specs that do not match this regular expression. Can be specified multiple times, values are ORed.
>   -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.
>   -test.bench regexp
>     	run only benchmarks matching regexp
>   -test.benchmem
>     	print memory allocations for benchmarks
>   -test.benchtime d
>     	run each benchmark for duration d (default 1s)
>   -test.blockprofile file
>     	write a goroutine blocking profile to file
>   -test.blockprofilerate rate
>     	set blocking profile rate (see runtime.SetBlockProfileRate) (default 1)
>   -test.count n
>     	run tests and benchmarks n times (default 1)
>   -test.coverprofile file
>     	write a coverage profile to file
>   -test.cpu list
>     	comma-separated list of cpu counts to run each test with
>   -test.cpuprofile file
>     	write a cpu profile to file
>   -test.failfast
>     	do not start new tests after the first test failure
>   -test.fuzz regexp
>     	run the fuzz test matching regexp
>   -test.fuzzcachedir string
>     	directory where interesting fuzzing inputs are stored (for use only by cmd/go)
>   -test.fuzzminimizetime value
>     	time to spend minimizing a value after finding a failing input (default 1m0s)
>   -test.fuzztime value
>     	time to spend fuzzing; default is to run indefinitely
>   -test.fuzzworker
>     	coordinate with the parent process to fuzz random values (for use only by cmd/go)
>   -test.list regexp
>     	list tests, examples, and benchmarks matching regexp then exit
>   -test.memprofile file
>     	write an allocation profile to file
>   -test.memprofilerate rate
>     	set memory allocation profiling rate (see runtime.MemProfileRate)
>   -test.mutexprofile string
>     	write a mutex contention profile to the named file after execution
>   -test.mutexprofilefraction int
>     	if >= 0, calls runtime.SetMutexProfileFraction() (default 1)
>   -test.outputdir dir
>     	write profiles to dir
>   -test.paniconexit0
>     	panic on call to os.Exit(0)
>   -test.parallel n
>     	run at most n tests in parallel (default 10)
>   -test.run regexp
>     	run only tests and examples matching regexp
>   -test.short
>     	run smaller test suite to save time
>   -test.shuffle string
>     	randomize the execution order of tests and benchmarks (default "off")
>   -test.testlogfile file
>     	write test action log to file (for use only by cmd/go)
>   -test.timeout d
>     	panic test binary after duration d (default 0, timeout disabled)
>   -test.trace file
>     	write an execution trace to file
>   -test.v
>     	verbose: print additional output
> Ginkgo ran 1 suite in 4.837645417s
> Test Suite Failed
> But this is not the case with ginkgo v1 which is very old. V2 is latest but need to understand the above issue in detail and provide a alternative or fix.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org