As seen here:
http://reports.vapour.ws/releases/3019/job/xx-run-unit-tests-lxc-wily-amd64/attempt/2006
This looks like a real assertion failure, where the obtained string has an unexpected [::1] line.
It may be a consistent failure. The wily unit tests have not passed on master for some time.
... obtained string = "" +
... "[::1]:57636\n" +
... "[2001:db8::1]:57636\n" +
... "0.1.2.3:57636\n" +
... "192.0.0.0:57636\n" +
... "8.8.8.8:57636\n" +
... "localhost:57636\n" +
... "[fc00::1]:57636\n" +
... "[fd00::1]:57636\n" +
... "10.0.0.1:57636\n"
... expected string = "" +
... "127.0.0.1:57636\n" +
... "[2001:db8::1]:57636\n" +
... "0.1.2.3:57636\n" +
... "192.0.0.0:57636\n" +
... "8.8.8.8:57636\n" +
... "localhost:57636\n" +
... "[fc00::1]:57636\n" +
... "[fd00::1]:57636\n" +
... "10.0.0.1:57636\n"
Other examples here:
http://reports.vapour.ws/releases/issue/55e48c17749a562deed133b5
I've investigated this a bit, as I remember the original test wasn't written to assum 127.0.0.1 is expected on top, but localhost.
The culprit commit which changed the behavior was: https:/
However, I can't reproduce this using go 1.2.1, or go 1.5 using master tip. Putting on hold for now (as intermittent and likely lower priority).