<p dir="auto">by <strong>jcowgar</strong>:</p>
<pre class="notranslate">What steps will reproduce the problem?
1. Create a source file:

package main

import "io"

func main() {
    fmt.Printf("Hello")
}

What is the expected output?
$ govet hello.go
hello.go:3 io package imported but not used
hello.go:6 fmt package is unknown/not imported

What do you see instead?
$ govet -v=true hello.go
Checking file hello.go
$

Which operating system are you using?
Linux (ArchLinux)

Which revision are you using?  (hg identify)
95d2ce135523 (release-branch.r57) release/release.r57.1

Please provide any additional information below.</pre>
<p dir="auto">by <strong>cgmurray</strong>:</p>
<pre class="notranslate">What steps will reproduce the problem?
run "go test -x ROOT_PACKAGE/..." with go 1.0.3 and tip (13e00572ed0b)

What is the expected output?
working directory is changed for every package with go 1.1, "cd ... or
equivalent"

What do you see instead?
working directory is not changed for every package as with go 1.0.3

Which compiler are you using (5g, 6g, 8g, gccgo)?
-

Which operating system are you using?
osx

Which version are you using?  (run 'go version')
go version devel +13e00572ed0b Thu Apr 18 17:37:21 2013 -0700 darwin/amd64

Please provide any additional information below.
This might break backwards compatibility. In the specific use-case a relative
library-path is set with -L</pre>