Re: [go-nuts] go test -c in go 1.13 does not include -test.timeout flag in binary?

2020-02-05 Thread Craig Rodrigues
On Monday, February 3, 2020 at 11:37:08 AM UTC-8, Ian Lance Taylor wrote: > > On Mon, Feb 3, 2020 at 8:13 AM Craig Rodrigues > wrote: > > > > Regarding the fact that I should not call flag.Parse() from inside an > init() method in my_test.go file, > > if a not

Re: [go-nuts] go test -c in go 1.13 does not include -test.timeout flag in binary?

2020-02-03 Thread Craig Rodrigues
On Friday, January 31, 2020 at 1:56:49 PM UTC-8, Ian Lance Taylor wrote: > > On Fri, Jan 31, 2020 at 10:33 AM Craig Rodrigues > wrote: > > > > Thanks for the response. I have a few questions. > > > > 1. In https://golang.org/pkg/flag/#Parse , would it be a

Re: [go-nuts] go test -c in go 1.13 does not include -test.timeout flag in binary?

2020-01-31 Thread Craig Rodrigues
On Friday, January 31, 2020 at 7:23:32 AM UTC-8, Ian Lance Taylor wrote: > > > Calling flag.Parse in an init function never worked reliably, unless > you took special care. Flags are themselves often defined in init > functions, so calling flag.Parse in an init function will see the > flags t

Re: [go-nuts] go test -c in go 1.13 does not include -test.timeout flag in binary?

2020-01-31 Thread Craig Rodrigues
On Thursday, January 30, 2020 at 11:03:04 PM UTC-8, Craig Rodrigues wrote: > > > > On Thursday, January 30, 2020 at 10:06:36 PM UTC-8, Ian Lance Taylor wrote: >> >> On Thu, Jan 30, 2020 at 9:43 PM Craig Rodrigues >> wrote: >> > I see here that this might

Re: [go-nuts] go test -c in go 1.13 does not include -test.timeout flag in binary?

2020-01-30 Thread Craig Rodrigues
On Thursday, January 30, 2020 at 10:06:36 PM UTC-8, Ian Lance Taylor wrote: > > On Thu, Jan 30, 2020 at 9:43 PM Craig Rodrigues > wrote: > > I see here that this might be related: > https://golang.org/doc/go1.13#testing > > > > Testing flags are

[go-nuts] go test -c in go 1.13 does not include -test.timeout flag in binary?

2020-01-30 Thread Craig Rodrigues
Hi, I ran a quick experiment in my source tree, and saw a difference in the behavior of "go test -c" between go 1.12 and go 1.13. EXPERIMENT 1: using docker image golang:1.12-alpine with go1.12.16 linux/amd64 --

[go-nuts] Cannot find libraries at go.pedge.io by Peter Edge

2019-09-24 Thread Craig Rodrigues
I have a package where the dependencies were vendored in a few years ago using govendor. I am trying to convert the vendor tree from govendor to go modules. I a having problems finding libraries written by Peter Edge, which had a DNS entry of go.pedge.io: "path": "go.pedge.io/env",

Re: [go-nuts] Invoke "go test" to execute exactly two specific tests?

2018-10-29 Thread Craig Rodrigues
On Mon, Oct 29, 2018 at 2:18 PM Jan Mercl <0xj...@gmail.com> wrote: > On Mon, Oct 29, 2018 at 10:09 PM Craig Rodrigues > wrote: > > > I can't figure out the regexp to match those two tests exactly. > > For example (not tested) > > $ go test -run '^Test(

Re: [go-nuts] Invoke "go test" to execute exactly two specific tests?

2018-10-29 Thread Craig Rodrigues
On Mon, Oct 29, 2018 at 2:16 PM Burak Serdar wrote: > On Mon, Oct 29, 2018 at 3:09 PM Craig Rodrigues > wrote: > > > > Hi, > > > > I have a suite of 20 tests, each test corresponding to a function: func > Test(). > > > > Out of the 20 tests, I

[go-nuts] Invoke "go test" to execute exactly two specific tests?

2018-10-29 Thread Craig Rodrigues
Hi, I have a suite of 20 tests, each test corresponding to a function: func Test(). Out of the 20 tests, I have two specific tests: func TestXG() func TestNiceSystem() I want to invoke *go test -test.run* to execute exactly those two tests, and nothing else. How can I invoke go test -te