@tw4452852 What does "sometimes" mean? Do you run golint multiple times?

Also, can you see if you still have packages installed that are compiled with an older compiler? Specifically, please look at (open in an editor) the file $GOROOT/pkg/darwi{n}_{a}md64/errors.aandletmeknowwhatthefirst20lineslooklike.Ifyoufinda$$ header followed by textual export data (rather that a $$B header) on line 9, you have stale packages and you should remove the $GOTOOT/pkg directory and recompile your std library.

If you have an up-to-date std library (all compiled with latest compiler), please provide more detailed instructions how to recreate this error (which version of golint, other packages installed). Thanks.

Please also note that we don't guarantee interoperability of package files between different compiler versions - and it looks like you're working with a compiler off tip.

@griesemer

What does "sometimes" mean? Do you run golint multiple times?

Yes, I run golint multiple times. Sometimes it finishes w/o any errors, but it panics sometimes. Also this panic only happens when I lint directory or package rather than single file.

Also, can you see if you still have packages installed that are compiled with an older compiler? Specifically, please look at (open in an editor) the file $GOROOT/pkg/darwi{n}_{a}md64/errors.aandletmeknowwhatthefirst20lineslooklike.Ifyoufinda$$ header followed by textual export data (rather that a $$B header) on line 9, you have stale packages and you should remove the $GOTOOT/pkg directory and recompile your std library.

I use the tip:

go version
go version devel +1472221 Thu Aug 25 00:19:32 2016 +0000 linux/amd64

And here is first 20 lines of $GOROOT/pkg/linux_amd64/errors.a:

cat -n $GOROOT/pkg/linux_amd64/errors.a| head -20
     1  !<arch>
     2  __.PKGDEF       0           0     0     644     373       `
     3  go object linux amd64 devel +1472221 Thu Aug 25 00:19:32 2016 +0000 X:framepointer
     4  build id "c0f935399829faef0243fb28d53100a38589efd2"
     5  ----
     6
     7  build id "c0f935399829faef0243fb28d53100a38589efd2"
     8
     9  $$B
    10  version 1
    11
    12  
text·2& errors  7|SGOROOT/src/errors/errors.goNew 
errorString
    13  s       Error<e·2esc:0x22 
                                  öV&TP<
                                       ¼¼¼ör
                                            ¼¼
    14  $$
    15  _go_.o          0           0     0     644     3152      `
    16  go object linux amd64 devel +1472221 Thu Aug 25 00:19:32 2016 +0000 X:framepointer
    17  build id "c0f935399829faef0243fb28d53100a38589efd2"
    18  ----
    19
    20

If you have an up-to-date std library (all compiled with latest compiler), please provide more detailed instructions how to recreate this error (which version of golint, other packages installed). Thanks.

As for golint version, I'm at this commit: c7bacac2b21ca01afa1dee0acf64df3ce047c28f

As for reproduce steps:

1. Just go get -u github.com/mholt/caddy/caddy
2. run golint several times: golint github.com/mholt/caddy/caddyhttp/proxy

I had a similar thing recently after upgrading to 1.7. My issue was with go vet (the same as #16112). I blew away the contents of $GOPATH/pkg and now it seems fine

@tw4452852 I cannot reproduce this on my machine, even with dozens of golint calls.

I'm at go version devel +8f3c8a3 Fri Aug 26 20:06:58 2016 +0000 darwin/amd64 (at commit 8f3c8a3).

I installed the same version of golint as you have.

And I installed caddy per the instructions (at commit 191ec27c261553c429cf5d6df2d14dce386417ff)

I'm not sure how it's possible for golint to pass sometimes and sometimes not, w/o changes to the files being linted. At least the import/export code is very deterministic.

I've tried this also with my latest devel version (not yet committed) that has better support for export format version skew detection - same result.

I suspect that you still have some package files that use an outdated format somewhere. I'd recommend blowing away all installed package files and to recompile with the latest compiler. I'm reasonably confident that this will solve the problem.

I have several pending changes (see #16881) which should hopefully make these errors a thing of the past.

Closing for now. If you still see a problem after re-installing your packages and upgrading to the latest compiler, please re-open this. Thanks.