Opened 8 years ago
Closed 8 years ago
#263 closed defect (fixed)
avoid using (external) network during tests
| Reported by: | Brian Warner | Owned by: | |
|---|---|---|---|
| Priority: | critical | Milestone: | 0.12.0 |
| Component: | network | Version: | 0.11.0 |
| Keywords: | Cc: |
Description (last modified by )
There's a debian bug against Foolscap for using the external network during the build process (which is against debian policy, since builds should be deterministic, and therefore not influenced by the outside world).
I think this is happening because one of the tests tries to reverse-DNS a name, or tries to ping the nameservers to determine which interface is pointing to the outside world. We should fix this.
This is pretty important, because the debian bug has foolscap (and Tahoe!) scheduled for removal from debian altogether on 22-Aug-2016.
Change History (4)
comment:1 Changed 8 years ago by
| Description: | modified (diff) |
|---|
comment:2 Changed 8 years ago by
| Priority: | major → critical |
|---|
comment:3 Changed 8 years ago by
comment:4 Changed 8 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Fixed, by releasing milestone:0.12.0
Note: See
TracTickets for help on using
tickets.
I think this was fixed in trunk back in september, in [bd960bf06], which changed
test_tub.pyto stop callingtub.setLocationAutomatically(). I need to manually test it (which I don't yet know how to do locally.. gotta figure out a tcpdump config), but I think that releasing milestone:0.12.0 should take care of this.