-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Finish, deploy DERP #2
Labels
Comments
Done. |
maisem
added a commit
that referenced
this issue
Jun 6, 2022
Signed-off-by: Maisem Ali <maisem@tailscale.com>
maisem
added a commit
that referenced
this issue
Jun 6, 2022
Signed-off-by: Maisem Ali <maisem@tailscale.com>
Soypete
pushed a commit
that referenced
this issue
Jun 14, 2022
Signed-off-by: Maisem Ali <maisem@tailscale.com>
DentonGentry
added a commit
that referenced
this issue
Sep 18, 2022
1. Use buildjet for the longer Linux CI workflows. 2. Use a self-hosted Windows runner. 3. Split CIFuzz into three pieces to run in parallel. workflow before #1 before #2 after #1 after #2 cifuzz.yml 8m 20s 7m 40s 4m 20s codeql-analysis.yml 4m 30s cached 2m 56s 2m 59s cross-darwin.yml 3m 10s 3m 19s 1m 33s 1m 30s cross-freebsd.yml 3m 33s 3m 10s 1m 28s 1m 22s cross-openbsd.yml 3m 4s 2m 36s 1m 29s 1m 22s cross-wasm.yml 1m 59s 2m 2s 1m 12s 1m 16s cross-windows.yml 2m 45s 3m 0s 1m 44s 1m 25s depaware.yml 25s 13s 16s 21s go_generate.yml 41s 40s 37s 31s go_mod_tidy.yml 31s 26s 36s 20s license.yml 10s 14s 23s 13s linux32.yml 4m 27s 4m 0s 1m 55s 2m 8s linux-race.yml 3m 54s 4m 7s 2m 22s 2m 12s linux.yml 4m 23s 4m 39s 2m 37s static-analysis.yml /gofmt 10s 15s 22s 23s /vet 1m 41s 2m 22s 52s 56s /staticcheck(linux, amd64) 2m 47s 2m 38s 1m 7s 1m 10s /staticcheck(windows, amd64) 2m 5s 2m 4s 1m 6s 1m 8s /staticcheck(darwin, amd64) 2m 14s 2m 20s 1m 10s 1m 10s /staticcheck(windows, 386) 2m 36s 1m 58s 1m 23s 1m 8s vm.yml 1m 30s 1m 32s 2m 31s 2m 23s windows.yml 6m 23s 6m 19s 3m 40s Signed-off-by: Denton Gentry <dgentry@tailscale.com>
DentonGentry
added a commit
that referenced
this issue
Sep 18, 2022
1. Use buildjet for the longer Linux CI workflows. 2. Use a self-hosted Windows runner. 3. Split CIFuzz into three pieces to run in parallel. workflow before #1 before #2 after #1 after #2 cifuzz.yml 8m 20s 7m 40s 4m 20s 3m 38s codeql-analysis.yml 4m 30s cached 2m 56s 2m 59s cross-darwin.yml 3m 10s 3m 19s 1m 33s 1m 30s cross-freebsd.yml 3m 33s 3m 10s 1m 28s 1m 22s cross-openbsd.yml 3m 4s 2m 36s 1m 29s 1m 22s cross-wasm.yml 1m 59s 2m 2s 1m 12s 1m 16s cross-windows.yml 2m 45s 3m 0s 1m 44s 1m 25s depaware.yml 25s 13s 16s 21s go_generate.yml 41s 40s 37s 31s go_mod_tidy.yml 31s 26s 36s 20s license.yml 10s 14s 23s 13s linux32.yml 4m 27s 4m 0s 1m 55s 2m 8s linux-race.yml 3m 54s 4m 7s 2m 22s 2m 12s linux.yml 4m 23s 4m 39s 2m 37s 2m 15s static-analysis.yml /gofmt 10s 15s 22s 23s /vet 1m 41s 2m 22s 52s 56s /staticcheck(linux, amd64) 2m 47s 2m 38s 1m 7s 1m 10s /staticcheck(windows, amd64) 2m 5s 2m 4s 1m 6s 1m 8s /staticcheck(darwin, amd64) 2m 14s 2m 20s 1m 10s 1m 10s /staticcheck(windows, 386) 2m 36s 1m 58s 1m 23s 1m 8s vm.yml 1m 30s 1m 32s 2m 31s 2m 23s windows.yml 6m 23s 6m 19s 3m 40s Signed-off-by: Denton Gentry <dgentry@tailscale.com>
maisem
added a commit
that referenced
this issue
Jun 30, 2023
Previously it would only print the failures without providing more information on which package the failures from. This commit makes it so that it prints out the package information as well as the attempt numbers. ``` ➜ tailscale.com git:(main) ✗ go run ./cmd/testwrapper ./cmd/... ok tailscale.com/cmd/derper ok tailscale.com/cmd/k8s-operator ok tailscale.com/cmd/tailscale/cli ok tailscale.com/cmd/tailscaled === RUN TestFlakeRun flakytest.go:38: flakytest: issue tracking this flaky test: https://github.com/tailscale/tailscale/issues/0 flakytest_test.go:41: First run in testwrapper, failing so that test is retried. This is expected. --- FAIL: TestFlakeRun (0.00s) FAIL tailscale.com/cmd/testwrapper/flakytest Attempt #2: Retrying flaky tests: ok tailscale.com/cmd/testwrapper/flakytest ``` Updates #8493 Signed-off-by: Maisem Ali <maisem@tailscale.com>
maisem
added a commit
that referenced
this issue
Jun 30, 2023
Previously it would only print the failures without providing more information on which package the failures from. This commit makes it so that it prints out the package information as well as the attempt numbers. ``` ➜ tailscale.com git:(main) ✗ go run ./cmd/testwrapper ./cmd/... ok tailscale.com/cmd/derper ok tailscale.com/cmd/k8s-operator ok tailscale.com/cmd/tailscale/cli ok tailscale.com/cmd/tailscaled === RUN TestFlakeRun flakytest.go:38: flakytest: issue tracking this flaky test: https://github.com/tailscale/tailscale/issues/0 flakytest_test.go:41: First run in testwrapper, failing so that test is retried. This is expected. --- FAIL: TestFlakeRun (0.00s) FAIL tailscale.com/cmd/testwrapper/flakytest Attempt #2: Retrying flaky tests: ok tailscale.com/cmd/testwrapper/flakytest ``` Updates #8493 Signed-off-by: Maisem Ali <maisem@tailscale.com>
maisem
added a commit
that referenced
this issue
Jun 30, 2023
Previously it would only print the failures without providing more information on which package the failures from. This commit makes it so that it prints out the package information as well as the attempt numbers. ``` ➜ tailscale.com git:(main) ✗ go run ./cmd/testwrapper ./cmd/... ok tailscale.com/cmd/derper ok tailscale.com/cmd/k8s-operator ok tailscale.com/cmd/tailscale/cli ok tailscale.com/cmd/tailscaled === RUN TestFlakeRun flakytest.go:38: flakytest: issue tracking this flaky test: https://github.com/tailscale/tailscale/issues/0 flakytest_test.go:41: First run in testwrapper, failing so that test is retried. This is expected. --- FAIL: TestFlakeRun (0.00s) FAIL tailscale.com/cmd/testwrapper/flakytest Attempt #2: Retrying flaky tests: ok tailscale.com/cmd/testwrapper/flakytest ``` Updates #8493 Signed-off-by: Maisem Ali <maisem@tailscale.com>
maisem
added a commit
that referenced
this issue
Jun 30, 2023
Previously it would only print the failures without providing more information on which package the failures from. This commit makes it so that it prints out the package information as well as the attempt numbers. ``` ➜ tailscale.com git:(main) ✗ go run ./cmd/testwrapper ./cmd/... ok tailscale.com/cmd/derper ok tailscale.com/cmd/k8s-operator ok tailscale.com/cmd/tailscale/cli ok tailscale.com/cmd/tailscaled === RUN TestFlakeRun flakytest.go:38: flakytest: issue tracking this flaky test: https://github.com/tailscale/tailscale/issues/0 flakytest_test.go:41: First run in testwrapper, failing so that test is retried. This is expected. --- FAIL: TestFlakeRun (0.00s) FAIL tailscale.com/cmd/testwrapper/flakytest Attempt #2: Retrying flaky tests: ok tailscale.com/cmd/testwrapper/flakytest ``` Updates #8493 Signed-off-by: Maisem Ali <maisem@tailscale.com>
maisem
added a commit
that referenced
this issue
Jun 30, 2023
Previously it would only print the failures without providing more information on which package the failures from. This commit makes it so that it prints out the package information as well as the attempt numbers. ``` ➜ tailscale.com git:(main) ✗ go run ./cmd/testwrapper ./cmd/... ok tailscale.com/cmd/derper ok tailscale.com/cmd/k8s-operator ok tailscale.com/cmd/tailscale/cli ok tailscale.com/cmd/tailscaled === RUN TestFlakeRun flakytest.go:38: flakytest: issue tracking this flaky test: https://github.com/tailscale/tailscale/issues/0 flakytest_test.go:41: First run in testwrapper, failing so that test is retried. This is expected. --- FAIL: TestFlakeRun (0.00s) FAIL tailscale.com/cmd/testwrapper/flakytest Attempt #2: Retrying flaky tests: ok tailscale.com/cmd/testwrapper/flakytest ``` Updates #8493 Signed-off-by: Maisem Ali <maisem@tailscale.com>
maisem
added a commit
that referenced
this issue
Jun 30, 2023
Previously it would only print the failures without providing more information on which package the failures from. This commit makes it so that it prints out the package information as well as the attempt numbers. ``` ➜ tailscale.com git:(main) ✗ go run ./cmd/testwrapper ./cmd/... ok tailscale.com/cmd/derper ok tailscale.com/cmd/k8s-operator ok tailscale.com/cmd/tailscale/cli ok tailscale.com/cmd/tailscaled === RUN TestFlakeRun flakytest.go:38: flakytest: issue tracking this flaky test: https://github.com/tailscale/tailscale/issues/0 flakytest_test.go:41: First run in testwrapper, failing so that test is retried. This is expected. --- FAIL: TestFlakeRun (0.00s) FAIL tailscale.com/cmd/testwrapper/flakytest Attempt #2: Retrying flaky tests: ok tailscale.com/cmd/testwrapper/flakytest ``` Updates #8493 Signed-off-by: Maisem Ali <maisem@tailscale.com>
maisem
added a commit
that referenced
this issue
Jun 30, 2023
Previously it would only print the failures without providing more information on which package the failures from. This commit makes it so that it prints out the package information as well as the attempt numbers. ``` ➜ tailscale.com git:(main) ✗ go run ./cmd/testwrapper ./cmd/... ok tailscale.com/cmd/derper ok tailscale.com/cmd/k8s-operator ok tailscale.com/cmd/tailscale/cli ok tailscale.com/cmd/tailscaled === RUN TestFlakeRun flakytest.go:38: flakytest: issue tracking this flaky test: https://github.com/tailscale/tailscale/issues/0 flakytest_test.go:41: First run in testwrapper, failing so that test is retried. This is expected. --- FAIL: TestFlakeRun (0.00s) FAIL tailscale.com/cmd/testwrapper/flakytest Attempt #2: Retrying flaky tests: ok tailscale.com/cmd/testwrapper/flakytest ``` Updates #8493 Signed-off-by: Maisem Ali <maisem@tailscale.com>
maisem
added a commit
that referenced
this issue
Jun 30, 2023
Previously it would only print the failures without providing more information on which package the failures from. This commit makes it so that it prints out the package information as well as the attempt numbers. ``` ➜ tailscale.com git:(main) ✗ go run ./cmd/testwrapper ./cmd/... ok tailscale.com/cmd/derper ok tailscale.com/cmd/k8s-operator ok tailscale.com/cmd/tailscale/cli ok tailscale.com/cmd/tailscaled === RUN TestFlakeRun flakytest.go:38: flakytest: issue tracking this flaky test: https://github.com/tailscale/tailscale/issues/0 flakytest_test.go:41: First run in testwrapper, failing so that test is retried. This is expected. --- FAIL: TestFlakeRun (0.00s) FAIL tailscale.com/cmd/testwrapper/flakytest Attempt #2: Retrying flaky tests: ok tailscale.com/cmd/testwrapper/flakytest ``` Updates #8493 Signed-off-by: Maisem Ali <maisem@tailscale.com>
alexelisenko
pushed a commit
to Control-D-Inc/tailscale
that referenced
this issue
Feb 15, 2024
Previously it would only print the failures without providing more information on which package the failures from. This commit makes it so that it prints out the package information as well as the attempt numbers. ``` ➜ tailscale.com git:(main) ✗ go run ./cmd/testwrapper ./cmd/... ok tailscale.com/cmd/derper ok tailscale.com/cmd/k8s-operator ok tailscale.com/cmd/tailscale/cli ok tailscale.com/cmd/tailscaled === RUN TestFlakeRun flakytest.go:38: flakytest: issue tracking this flaky test: https://github.com/tailscale/tailscale/issues/0 flakytest_test.go:41: First run in testwrapper, failing so that test is retried. This is expected. --- FAIL: TestFlakeRun (0.00s) FAIL tailscale.com/cmd/testwrapper/flakytest Attempt tailscale#2: Retrying flaky tests: ok tailscale.com/cmd/testwrapper/flakytest ``` Updates tailscale#8493 Signed-off-by: Maisem Ali <maisem@tailscale.com> Signed-off-by: Alex Paguis <alex@windscribe.com>
clairew
added a commit
that referenced
this issue
Mar 13, 2024
# This is the 1st commit message: cmd/tailscale, ipn/ipnlocal: add suggest exit node CLI option wip # The commit message #2 will be skipped: # wip
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tracking bug for deploying DERP, the "Detour Encrypted Routing Protocol".
Tailscale tries to send traffic directly between peers, traversing NATs as needed, but sometimes no path is possible or it takes some time to find a path, so DERP is the ultimate fallback that routes encrypted packets through the cloud.
DERP is somewhat implemented & tested, but not enough, and it's not yet deployed + used.
The text was updated successfully, but these errors were encountered: