Summary: | net-proxy/obfsproxy-0.1.4: tests got stuck for over 9 and a half hours | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | New packages | Assignee: | Anthony Basile <blueness> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://tinderboxlogs.s3.amazonaws.com/tbamd64.excelsior.flameeyes.eu/net-proxy%3Aobfsproxy-0.1.4%3A20130102-140759.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Diego Elio Pettenò (RETIRED)
2013-01-03 00:07:07 UTC
Diego, are you doing this on an ipv6 only box? The tests work for me except for a python2-only script which I can easily fixup. It has no connectivity to the outside, either IPv4 or IPv6. (In reply to comment #2) > It has no connectivity to the outside, either IPv4 or IPv6. Okay this happens if there is no loopback. Does the tinderbox provide lo? If it doesn't it seems to me that it should since almost all systems would have a loopback. If it does, then something else is going on. I tested again, and as long as you have a loop back, the tests work fine. I think this is one of those rare tinderbox artifacts. I doubt it's invalid. The lo interface is present and localhost is accessible, but there is no network connectivity and eth0 only has IPv6 — did you try in those conditions? (In reply to comment #5) > I doubt it's invalid. The lo interface is present and localhost is > accessible, but there is no network connectivity and eth0 only has IPv6 — > did you try in those conditions? No, I just tried one interface, lo up/down. No eth0, no ipv4, no ipv6. So maybe the the fact that eth0 is up and has an ipv6 causes problems. All said, I'm not against RESTRICT="test". As stated, the only way I hit it was with zero interfaces. With just lo up, and localhost accessible, it worked. Okay, I have a hunch it might be thrown off by eth0 existing but being IPv6-only — can you try to reproduce on your side so that we can see if that's the case? I am considering putting in production IPv6-only systems, so I'd like to see what's the case with this. (In reply to comment #7) > Okay, I have a hunch it might be thrown off by eth0 existing but being > IPv6-only — can you try to reproduce on your side so that we can see if > that's the case? > > I am considering putting in production IPv6-only systems, so I'd like to see > what's the case with this. Yep, confirmed. FYI, obfsproxy works with tor, and both work only with IPv4. |