tailscale/cmd/testwrapper, branch debug-testwrapper

debug testwrapper

2026-01-29T13:47:47Z

Change-Id: Idf8e35297c1c353588211d7f1c572f03b040e43b Signed-off-by: Tom Proctor

cmd/testwrapper: show "(cached)" for packages that hit the cache

2026-01-29T02:25:03Z

We weren't parsing that out previously, making it look like tests were re-running even though they were cached. Updates tailscale/go#150 Updates tailscale/corp#28679 Updates tailscale/corp#34696 Change-Id: I6254362852a82ccc86ac464a805379d941408dad Signed-off-by: Brad Fitzpatrick

cmd/testwrapper/flakytest: skip flaky tests if TS_SKIP_FLAKY_TESTS set

2026-01-28T16:54:33Z

This is for a future test scheduler, so it can run potentially flaky tests separately, doing all the non-flaky ones together in one batch. Updates tailscale/corp#28679 Change-Id: Ic4a11f9bf394528ef75792fd622f17bc01a4ec8a Signed-off-by: Brad Fitzpatrick

all: remove AUTHORS file and references to it

2026-01-23T23:49:45Z

This file was never truly necessary and has never actually been used in the history of Tailscale's open source releases. A Brief History of AUTHORS files --- The AUTHORS file was a pattern developed at Google, originally for Chromium, then adopted by Go and a bunch of other projects. The problem was that Chromium originally had a copyright line only recognizing Google as the copyright holder. Because Google (and most open source projects) do not require copyright assignemnt for contributions, each contributor maintains their copyright. Some large corporate contributors then tried to add their own name to the copyright line in the LICENSE file or in file headers. This quickly becomes unwieldy, and puts a tremendous burden on anyone building on top of Chromium, since the license requires that they keep all copyright lines intact. The compromise was to create an AUTHORS file that would list all of the copyright holders. The LICENSE file and source file headers would then include that list by reference, listing the copyright holder as "The Chromium Authors". This also become cumbersome to simply keep the file up to date with a high rate of new contributors. Plus it's not always obvious who the copyright holder is. Sometimes it is the individual making the contribution, but many times it may be their employer. There is no way for the proejct maintainer to know. Eventually, Google changed their policy to no longer recommend trying to keep the AUTHORS file up to date proactively, and instead to only add to it when requested: https://opensource.google/docs/releasing/authors. They are also clear that: > Adding contributors to the AUTHORS file is entirely within the > project's discretion and has no implications for copyright ownership. It was primarily added to appease a small number of large contributors that insisted that they be recognized as copyright holders (which was entirely their right to do). But it's not truly necessary, and not even the most accurate way of identifying contributors and/or copyright holders. In practice, we've never added anyone to our AUTHORS file. It only lists Tailscale, so it's not really serving any purpose. It also causes confusion because Tailscalars put the "Tailscale Inc & AUTHORS" header in other open source repos which don't actually have an AUTHORS file, so it's ambiguous what that means. Instead, we just acknowledge that the contributors to Tailscale (whoever they are) are copyright holders for their individual contributions. We also have the benefit of using the DCO (developercertificate.org) which provides some additional certification of their right to make the contribution. The source file changes were purely mechanical with: git ls-files | xargs sed -i -e 's/\(Tailscale Inc &\) AUTHORS/\1 contributors/g' Updates #cleanup Change-Id: Ia101a4a3005adb9118051b3416f5a64a4a45987d Signed-off-by: Will Norris

cmd/testwrapper/flakytest: use t.Attr annotation on flaky tests

2025-10-06T17:58:48Z

Updates #17460 Change-Id: I7381e9a6dd73514c73deb6b863749eef1a87efdc Signed-off-by: Brad Fitzpatrick

.github/workflows: shard the Windows builder

2025-06-20T13:11:11Z

It's one of the slower ones, so split it up into chunks. Updates tailscale/corp#28679 Change-Id: I16a5ba667678bf238c84417a51dda61baefbecf7 Signed-off-by: Brad Fitzpatrick

cmd/testwrapper: print failed tests preventing retry (#15270)

2025-03-13T14:21:29Z

Updates tailscale/corp#26637 Signed-off-by: Paul Scott

cmd/testwrapper: Display package-level output

2025-03-04T16:01:28Z

Updates tailscale/corp#26861 Signed-off-by: James Sanderson

cmd/testwrapper/flakytest: add Marked to check if in flakytest (#15119)

2025-02-24T21:26:41Z

Updates tailscale/corp#26637 Signed-off-by: Paul Scott

go.toolchain.branch: update to Go 1.24 (#15016)

2025-02-19T18:55:49Z

* go.toolchain.branch: update to Go 1.24 Updates #15015 Change-Id: I29c934ec17e60c3ac3264f30fbbe68fc21422f4d Signed-off-by: Brad Fitzpatrick * cmd/testwrapper: fix for go1.24 Updates #15015 Signed-off-by: Paul Scott * go.mod,Dockerfile: bump to Go 1.24 Also bump golangci-lint to a version that was built with 1.24 Updates #15015 Signed-off-by: Andrew Lytvynov --------- Signed-off-by: Brad Fitzpatrick Signed-off-by: Paul Scott Signed-off-by: Andrew Lytvynov Co-authored-by: Paul Scott Co-authored-by: Andrew Lytvynov