-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
flake: TestStoreWatch panicked #13068
Comments
@marun -- can you help track down this flake? |
The panic is driven by this assertion: https://github.com/openshift/origin/blob/release-1.5/vendor/github.com/boltdb/bolt/cursor.go#L155 This looks the same as this issue currently open in etcd: |
so similar to the above, somewhere a db is being closed while not waiting for tx to finish. i am inclined to make this a p2 since it has not been reported outside of this test case. |
which is the exact same as this upstream issue: |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_check_future/455/consoleFull#
-4669372365898c58db7602c31c0eab717
The text was updated successfully, but these errors were encountered: