TestProfile fails
legrostdg opened this issue · 5 comments
legrostdg commented
I'm trying to create a Debian package for profile. The test TestProfile fails during the build of the packages:
go test -v -p 4 github.com/pkg/profile
=== RUN TestProfile
--- FAIL: TestProfile (1.75s)
profile_test.go:174: default profile (cpu)
profile_test.go:174: memory profile
profile_test.go:174: memory profile (rate 2048)
profile_test.go:174: double start
profile_test.go:174: block profile
profile_test.go:174: profile path
profile_test.go:174: profile path error
profile_test.go:194: stderr: wanted '[could not create initial output]', got '2017/05/09 06:50:47 profile: cpu profiling enabled, README.md/cpu.pprof
2017/05/09 06:50:47 profile: cpu profiling disabled, README.md/cpu.pprof
'
profile_test.go:209: expected error
profile_test.go:174: multiple profile sessions
profile_test.go:174: profile quiet
davecheney commented
What happens if you skip the -v and -p flags
…On Tue, May 9, 2017 at 4:59 PM, legrostdg ***@***.***> wrote:
I'm trying to create a Debian package for profile. The test TestProfile
fails during the build of the packages:
go test -v -p 4 github.com/pkg/profile
=== RUN TestProfile
--- FAIL: TestProfile (1.75s)
profile_test.go:174: default profile (cpu)
profile_test.go:174: memory profile
profile_test.go:174: memory profile (rate 2048)
profile_test.go:174: double start
profile_test.go:174: block profile
profile_test.go:174: profile path
profile_test.go:174: profile path error
profile_test.go:194: stderr: wanted '[could not create initial output]', got '2017/05/09 06:50:47 profile: cpu profiling enabled, README.md/cpu.pprof
2017/05/09 06:50:47 profile: cpu profiling disabled, README.md/cpu.pprof
'
profile_test.go:209: expected error
profile_test.go:174: multiple profile sessions
profile_test.go:174: profile quiet
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#39>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAcA4O4sS5ymKLbvM_TTlN3WSkFrwFuks5r4A7cgaJpZM4NU5d4>
.
legrostdg commented
go test github.com/pkg/profile
--- FAIL: TestProfile (1.78s)
profile_test.go:174: default profile (cpu)
profile_test.go:174: memory profile
profile_test.go:174: memory profile (rate 2048)
profile_test.go:174: double start
profile_test.go:174: block profile
profile_test.go:174: profile path
profile_test.go:174: profile path error
profile_test.go:194: stderr: wanted '[could not create initial output]', got '2017/05/09 07:42:52 profile: cpu profiling enabled, README.md/cpu.pprof
2017/05/09 07:42:52 profile: cpu profiling disabled, README.md/cpu.pprof
'
profile_test.go:209: expected error
profile_test.go:174: multiple profile sessions
profile_test.go:174: profile quiet
FAIL
FAIL github.com/pkg/profile 1.784s
davecheney commented
Ok, it was worth a shot, let me take a look at that test.
…On Tue, 9 May 2017, 17:44 legrostdg ***@***.***> wrote:
go test github.com/pkg/profile
--- FAIL: TestProfile (1.78s)
profile_test.go:174: default profile (cpu)
profile_test.go:174: memory profile
profile_test.go:174: memory profile (rate 2048)
profile_test.go:174: double start
profile_test.go:174: block profile
profile_test.go:174: profile path
profile_test.go:174: profile path error
profile_test.go:194: stderr: wanted '[could not create initial output]', got '2017/05/09 07:42:52 profile: cpu profiling enabled, README.md/cpu.pprof
2017/05/09 07:42:52 profile: cpu profiling disabled, README.md/cpu.pprof
'
profile_test.go:209: expected error
profile_test.go:174: multiple profile sessions
profile_test.go:174: profile quiet
FAIL
FAIL github.com/pkg/profile 1.784s
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#39 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAAcA0CFLDsR-awJEK4BWsXn_h9-JfWLks5r4BlrgaJpZM4NU5d4>
.
legrostdg commented
Thanks! Could you publish a new release with this fix?
davecheney commented