Skip to content
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

TestVSphereLoginByToken data race #20219

Closed
sjenning opened this issue Jul 5, 2018 · 6 comments
Closed

TestVSphereLoginByToken data race #20219

sjenning opened this issue Jul 5, 2018 · 6 comments
Assignees
Labels
kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/master

Comments

@sjenning
Copy link
Contributor

sjenning commented Jul 5, 2018

This is a new test as of kube 1.11

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/20158/pull-ci-origin-unit/900/

=== RUN   TestVSphereLoginByToken
E0705 17:13:06.921738    9479 connection.go:134] Logout failed: Post https://127.0.0.1:36902/sdk: dial tcp 127.0.0.1:36902: connect: connection refused
==================
WARNING: DATA RACE
Write at 0x00c4200fbbc0 by goroutine 48:
  github.com/openshift/origin/vendor/k8s.io/kubernetes/pkg/cloudprovider/providers/vsphere/vclib.(*VSphereConnection).Connect()
      /go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/pkg/cloudprovider/providers/vsphere/vclib/connection.go:59 +0x3ff
  github.com/openshift/origin/vendor/k8s.io/kubernetes/pkg/cloudprovider/providers/vsphere.TestVSphereLoginByToken()
      /go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/pkg/cloudprovider/providers/vsphere/vsphere_test.go:246 +0x335
  testing.tRunner()
      /usr/local/go/src/testing/testing.go:777 +0x16d

Previous read at 0x00c4200fbbc0 by goroutine 5:
  github.com/openshift/origin/vendor/k8s.io/kubernetes/pkg/cloudprovider/providers/vsphere.logout()
      /go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/pkg/cloudprovider/providers/vsphere/vsphere.go:496 +0x13b

Goroutine 48 (running) created at:
  testing.(*T).Run()
      /usr/local/go/src/testing/testing.go:824 +0x564
  testing.runTests.func1()
      /usr/local/go/src/testing/testing.go:1063 +0xa4
  testing.tRunner()
      /usr/local/go/src/testing/testing.go:777 +0x16d
  testing.runTests()
      /usr/local/go/src/testing/testing.go:1061 +0x4e1
  testing.(*M).Run()
      /usr/local/go/src/testing/testing.go:978 +0x2cd
  main.main()
      _testmain.go:112 +0x324

Goroutine 5 (running) created at:
  runtime.createfing()
      /usr/local/go/src/runtime/mfinal.go:156 +0x61
  os.NewFile()
      /usr/local/go/src/os/file_unix.go:79 +0x55
  os.init()
      /usr/local/go/src/os/file.go:58 +0x418
  main.init()
      <autogenerated>:1 +0x96
==================
--- FAIL: TestVSphereLoginByToken (0.31s)
	testing.go:730: race detected during execution of test

@smarterclayton

@sjenning sjenning added kind/test-flake Categorizes issue or PR as related to test flakes. sig/master labels Jul 5, 2018
@sjenning
Copy link
Contributor Author

sjenning commented Jul 5, 2018

added here kubernetes/kubernetes#63824

@sjenning
Copy link
Contributor Author

sjenning commented Jul 5, 2018

looks like all tests share a VSphereInstance so running them in parallel could cause this

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 3, 2018
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 2, 2018
@openshift-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci-robot
Copy link

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/master
Projects
None yet
Development

No branches or pull requests

4 participants