archive
/
tailscale
mirror of https://github.com/tailscale/tailscale/
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
7,116 Commits
966 Branches
204 Tags
117 MiB
Commit Graph

313 Commits (94a4f701c2fbaf914975c15c458f8b3a500e9d9e)

Author SHA1 Message Date
David Anderson 771eb05bcb tstest/natlab: first network attached becomes the default route. 
Signed-off-by: David Anderson <danderson@tailscale.com>
David Anderson f2e5da916a tstest/natlab: allow sensible default construction of networks. 
Add a test for LAN->LAN traffic.

Signed-off-by: David Anderson <danderson@tailscale.com>
Brad Fitzpatrick 97910ce712 tstest/natlab: remove unused PacketConner type
Brad Fitzpatrick 14b4213c17 tstest/natlab: add missing tests from earlier commits 
Now you can actually see that packet delivery works.

Pairing with @danderson
Brad Fitzpatrick 3f4f1cfe66 tstest/natlab: basic NAT-free packet delivery works 
Pairing with @danderson
Brad Fitzpatrick a477e70632 tstest/natlab: network address allocation 
Pairing with @danderson
Brad Fitzpatrick bb1a9e4700 tstest/natlab: bit more of in-memory network testing package 
Pairing with @danderson
Brad Fitzpatrick 23c93da942 tstest/natlab: start of in-memory network testing package 
Pairing with @danderson
Brad Fitzpatrick 5ec7ac1d02 tstest: document PanicOnLog
Avery Pennarun 4f128745d8 magicsock/test: oops, fix a data race in nested-test logf hack. 
Signed-off-by: Avery Pennarun <apenwarr@tailscale.com>
Avery Pennarun 08acb502e5 Add tstest.PanicOnLog(), and fix various problems detected by this. 
If a test calls log.Printf, 'go test' horrifyingly rearranges the
output to no longer be in chronological order, which makes debugging
virtually impossible. Let's stop that from happening by making
log.Printf panic if called from any module, no matter how deep, during
tests.

This required us to change the default error handler in at least one
http.Server, as well as plumbing a bunch of logf functions around,
especially in magicsock and wgengine, but also in logtail and backoff.

To add insult to injury, 'go test' also rearranges the output when a
parent test has multiple sub-tests (all the sub-test's t.Logf is always
printed after all the parent tests t.Logf), so we need to screw around
with a special Logf that can point at the "current" t (current_t.Logf)
in some places. Probably our entire way of using subtests is wrong,
since 'go test' would probably like to run them all in parallel if you
called t.Parallel(), but it definitely can't because the're all
manipulating the shared state created by the parent test. They should
probably all be separate toplevel tests instead, with common
setup/teardown logic. But that's a job for another time.

Signed-off-by: Avery Pennarun <apenwarr@tailscale.com>
Avery Pennarun e0b666c5d2 tstest.ResourceCheck: clarify success message. 
Inclusion of the word "assert" made it seem like a failure, even though
it was supposed to be identifying the name of the function (Assert()).

Signed-off-by: Avery Pennarun <apenwarr@tailscale.com>
David Anderson 0038223632 tstest: rename from testy. 
Signed-off-by: David Anderson <danderson@tailscale.com>