Test failures in Go 1.8 about go-agent

[nathany]

Aside: Is there any sort of CI system setup to run these tests? Would you consider a test matrix for multiple Go versions using something like TravisCI? Let me know if you would like a PR for that.

[nathany]

The failure in TestCopyConfigReferenceFieldsPresent is due to the way numbers are being encoded in Go 1.8.

"Marshal encodes floating-point numbers using the same format as in ES6, preferring decimal (not exponential) notation for a wider range of values. In particular, all floating-point integers up to 264 format the same as the equivalent int64 representation." https://beta.golang.org/doc/go1.8

I don't imagine that related to why we stopped seeing any metrics in New Relic. It's just a change that the string comparison in this test doesn't account for.

[willnewrelic]

Hi @nathany

Thanks for the heads up! We will fix this shortly.

We have a CI system internally: We are looking into what system would work for both public and private development.

[nathany]

Thanks Will.

I think the issue we experienced with losing New Relic data wasn't related to Go 1.8, but instead from switching from golang:1.7.4-alpine (Docker) to alpine:3.5. I don't see why New Relic go-agent would require the Go compiler, but perhaps there is something else it needs that exists in the golang image?

As far as this issue, maybe using smaller (single digit?) values would satisfy the tests across both Go 1.7 and Go 1.8, assuming that the tests stick with hard coded JSON output.

[willnewrelic]

@nathany I don't have any insight into how the Docker change could affect agent behavior. Are you still experiencing this problem? If so, let's address it in a separate issue or support ticket.

Go 1.8 tests fixed as part of the latest 1.6.0 release! Thanks for bringing this to our attention!

[nathany]

Thanks @willnewrelic.