myriation/headscale
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity

add comment about poor error handling when headscale isnt becoming available

Browse source
This commit is contained in:
Kristoffer Dalby 2021-10-04 14:16:37 +01:00
parent 2090a13dcd
commit 772541afab
No known key found for this signature in database
GPG key ID: 09F62DC067465735
1 changed files with 5 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
integration_test.go
View file

@ -258,7 +258,11 @@ func (s *IntegrationTestSuite) SetupSuite() {
} }
return nil return nil
}); err != nil { }); err != nil {
log.Fatalf("Could not connect to docker: %s", err) // TODO(kradalby): If we cannot access headscale, or any other fatal error during
// test setup, we need to abort and tear down. However, testify does not seem to
// support that at the moment:
// https://github.com/stretchr/testify/issues/849
return // fmt.Errorf("Could not connect to headscale: %s", err)
} }
fmt.Println("headscale container is ready") fmt.Println("headscale container is ready")