Go build error: no non-test Go files in <dir>

Question

Getting an error when trying to run go build ./... from my $GOPATH/src .

no non-test Go files in <dir>

The error is correct there are no test files in <dir> but why is that causing a compile error? Is it a bug?

The error says there are no non-test files. There's nothing to build in that directory. — Mr_Pink
– Mr_Pink, Commented Oct 23, 2017 at 21:54
"from my $GOPATH/src" that doesn't sound right - that builds everything - what are you trying to build? — fstanis
– fstanis, Commented Oct 23, 2017 at 22:27
You are aware that go build ./... doesn't do anything, other than building things and throwing away the results, right? — Mr_Pink
– Mr_Pink, Commented Oct 23, 2017 at 22:44

Clintm · Accepted Answer · 2017-11-13 16:46:52Z

5

Calling it a bug… the build shouldn't fail if the tests compile. Filed here: https://github.com/golang/go/issues/22409

The bug I filed was a duplicate of https://github.com/golang/go/issues/8279 looks like it was broken in 1.3.

edited Nov 13, 2017 at 16:46

answered Oct 23, 2017 at 23:13

Clintm

4,9443 gold badges46 silver badges61 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Kenny Grant · Accepted Answer · 2017-10-30 22:48:22Z

3

I don't think this is a bug, unless you see somewhere in the docs that contradicts this behaviour you should probably close the issue you've created.

Tests in go normally live in the package they are testing. You have made a new package with package main at the top (invalid if you also have main elsewhere), and then have included no go source files in that tests/main package (invalid as package has no go source files apart from tests, which the compiler complains about explicitly).

Possible solutions for you (assuming this isn't just a hypothetical question):

Move tests for main to test_main.go (this is what readers will expect)
Add doc.go file to your tests pkg and call it package tests in both files

The reason for putting tests in the same package is to ensure they have access to the entire package, if you want to split them to another package you'll find you have to test as an external user of the pkg - this may be painful. Main is also a special case as well as you don't normally import it.

answered Oct 30, 2017 at 22:48

Kenny Grant

9,7232 gold badges35 silver badges47 bronze badges

1 Comment

Kenny Grant Over a year ago

That issue is closed with won’t fix

Morningxxx · Accepted Answer · 2018-11-22 14:16:19Z

1

First, check your $GOPATH has been set correctly. Learn more at here.

Then, check if any '_' in your file name. Remove these '_'s and try again. ;-)

edited Nov 22, 2018 at 14:16

answered Nov 22, 2018 at 10:31

Morningxxx

555 bronze badges

Collectives™ on Stack Overflow

Go build error: no non-test Go files in <dir>

3 Answers 3

Comments

1 Comment

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related