Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

syscall: routing message parser seems to be wrong on freebsd-386-gce101 #9707

Closed
mikioh opened this issue Jan 28, 2015 · 9 comments
Closed

syscall: routing message parser seems to be wrong on freebsd-386-gce101 #9707

mikioh opened this issue Jan 28, 2015 · 9 comments
Milestone

Comments

@mikioh
Copy link
Contributor

@mikioh mikioh commented Jan 28, 2015

See http://build.golang.org/log/c66156b3f8d5fdd6f2480c180ed627a58007c9f0

interface_test.go:76: "lo0": flags "up|loopback|multicast", ifindex 2, mtu 16384
interface_test.go:77: hardware address ""
interface_test.go:161: unexpected value: &net.IPNet{IP:net.IP{0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, Mask:net.IPMask{0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff}}
interface_test.go:178: interface address "0:0:fe80::/64"
interface_test.go:178: interface address "127.0.0.1/8"

The output on loopback interface must be

interface_test.go:178: interface address "::1/128"
interface_test.go:178: interface address "fe80::1/64"
interface_test.go:178: interface address "127.0.0.1/8"
@mikioh
Copy link
Contributor Author

@mikioh mikioh commented Jan 28, 2015

Hm, #8203, looks like I was wrong, it hurts the net package.

@bradfitz
Copy link
Contributor

@bradfitz bradfitz commented Jan 28, 2015

@rakyll, this is a perfect example of when we'd want to be able to say "just run gomote create freebsd-amd64-gce101 and have your own dev environment of this builder type".

@mikioh, we're almost there, but the cmd/gomote tool doesn't yet auto-create images in your GCE project from the public images URLs (which aren't associated with the builder types).

Mikio, are you able to debug this on your own? Or do you want instructions on how to use gomote for now?

@mikioh mikioh added the repo-main label Jan 28, 2015
@mikioh mikioh added this to the Go1.5Maybe milestone Jan 28, 2015
@mikioh
Copy link
Contributor Author

@mikioh mikioh commented Jan 28, 2015

@bradfitz I think I can manage this issue; what I need is a time for reading kernel code.

Perhaps I had to ask again at that time even though Mr. Pike rejected a CL for #8203. I think I stashed that patch but it disappears now.

@bradfitz
Copy link
Contributor

@bradfitz bradfitz commented Jan 28, 2015

Oh, I notice this fails only on freebsd-386-gce101 and not amd64.

Note that the FreeBSD-386 builder is a 64-bit kernel (same VM as the amd64 builder) but just runs with GOARCH=386.

@mikioh
Copy link
Contributor Author

@mikioh mikioh commented Jan 28, 2015

Note that the FreeBSD-386 builder is a 64-bit kernel (same VM as the amd64 builder) but just runs with GOARCH=386.

Cool, I've never imagined a use case like that. Certainly that's one of the root causes.

@mikioh mikioh self-assigned this Feb 6, 2015
@bradfitz
Copy link
Contributor

@bradfitz bradfitz commented Feb 7, 2015

@mikioh, can we get this fixed? This builder has been broken for too long.

@mikioh
Copy link
Contributor Author

@mikioh mikioh commented Feb 7, 2015

@bradfitz, sure, the root causes are a) broken platform recognition stuff, and b) lazy parsers that try to ignore uninteresting messages so hard. but not write a patch yet. if you hurry, will work on this before fixing other issues.

@bradfitz
Copy link
Contributor

@bradfitz bradfitz commented Feb 7, 2015

Yes, I'd always prioritize getting the builders "ok" before new features. A red builder hides other problems. Thanks.

@mikioh
Copy link
Contributor Author

@mikioh mikioh commented Feb 10, 2015

@mikioh mikioh closed this in 69275ee Feb 20, 2015
@mikioh mikioh modified the milestones: Go1.5Maybe, Go1.5 Feb 20, 2015
@mikioh mikioh removed their assignment May 27, 2015
@golang golang locked and limited conversation to collaborators Jun 25, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.