-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
Go 1.13: flag provided but not defined: -test.timeout #33475
Comments
It is likely #31859. Somewhere in the code, it is calling flag.Parse inside an init() function. |
@eclipseo, please confirm whether the panic is occurring during package initialization. |
I don't see any Init function or flag.Parse in github.com/karlseguin/ccache Might be called by the dependency in https://github.com/karlseguin/expect/blob/ecc6aa3406d03d381160d52b8a76268abdb14321/runner.go#L36 ccache:
github.com/karlseguin/expect:
|
Yep, that looks like it. Presumably you'll want to send a PR to fix that dependency (or drop your program's use of it) for 1.13. |
Duplicate of #31859 |
Ok, thanks for the help! |
- The README now has the latest cli arguments listed - The pipeline no longer runs the single unit test due to a strange newer issue with go test (see golang/go#33475) - Removed TODO file, as this information is tracked in github issues - Merge remote-tracking branch 'upstream/master' - Ran go mod tidy
- The README now has the latest cli arguments listed - The pipeline no longer runs the single unit test due to a strange newer issue with go test (see golang/go#33475) - Removed TODO file, as this information is tracked in github issues - Merge remote-tracking branch 'upstream/master' - Ran go mod tidy - Puppet - the message to show modules on the puppet master was moved so that it will list modules before MOSE introduces a rogue module
Why would it break in an init() func but not when it's parsed after that? |
@ORESoftware This issue is closed. Also I'm not sure what you are asking. See the third paragraph in https://golang.org/doc/go1.13#testing. |
see @agnivade comment above dude |
@ORESoftware For questions about Go please use a forum: https://golang.org/wiki/Questions. Thanks. The answer to your question is, as described at the linked issue #31859, that the testing package defines its flags in |
Following #28147, I'm encountering this error with github.com/karlseguin/ccache on 1.13 beta 1:
I'm not sure how to tackle this, is it an issue with ccache tests or from Go itself?
The text was updated successfully, but these errors were encountered: