Tests fail on Go develoment builds.

[hansrodtang]

Probably not the most serious of issues, but I thought I should comment on it.

The parsing in goexecutable.coffee fetches the name from the version string, which in development builds does not contain the word "go", making the tests fail.

The test failing is this one here: goexecutable-spec.coffee

Getting go name from components[0] could solve line 38, not sure how to handle version testing, or if it is even needed.

[joefitzgerald]

Yeah, it's probably not even critical to have those assertions. What is the value for name in a development build?

[hansrodtang]

The entire output of go version:

go version devel +723ca3789b88 Sat Nov 15 13:27:05 2014 +1100 darwin/amd64

[joefitzgerald]

Release candidates and betas seem to have information in go version that would make the tests pass. Are you referring to scenarios where you build go from source?

[hansrodtang]

Yes, development builds which are just snapshots of the current development. Betas/RCs have prepared versioning.

So yeah, probably a mildly obscure issue, but if all other tests complete just fine, the version number shouldn't really matter.

[joefitzgerald]

@hansrodtang Can you test with the latest in master and let me know if this does the trick?

[hansrodtang]

After removing the code.google.com import path for the cover tool (Go 1.4 does not accept it) it builds just fine (Build log)