-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
acceptance: TestDockerCLI/test_extern_dir.tcl/runMode=docker failed #76448
Comments
acceptance.TestDockerCLI failed with artifacts on master @ b16a845e7c661d72a538ed3f919d0156572440c3:
Help
See also: How To Investigate a Go Test Failure (internal)
Same failure on other branches
|
error is:
(note that this test is run with multitenant=false) cc @knz to triage |
acceptance.TestDockerCLI failed with artifacts on master @ 8d0a1773a6b55f06c04ea77e6a39426e32ba9a63:
Help
See also: How To Investigate a Go Test Failure (internal)
Same failure on other branches
|
acceptance.TestDockerCLI failed with artifacts on master @ d05e52e6dffccb28b59cd4df379c85582ef7b878:
Help
See also: How To Investigate a Go Test Failure (internal)
Same failure on other branches
|
acceptance.TestDockerCLI failed with artifacts on master @ 9b45e990d5ddbbd6da13e8d3e312bb251fe0233a:
Help
See also: How To Investigate a Go Test Failure (internal)
Same failure on other branches
|
acceptance.TestDockerCLI failed with artifacts on master @ 2867db02330e173509c0bffbc7bf7037ef55b3c5:
Help
See also: How To Investigate a Go Test Failure (internal)
Same failure on other branches
|
acceptance.TestDockerCLI failed with artifacts on master @ 1b7bcfa9a06293835891da5086b909218334c393:
Help
See also: How To Investigate a Go Test Failure (internal)
Same failure on other branches
|
The latest failure looks like a problem with
Not able to repro though. Going to wait and see if this fails again before closing. |
acceptance.TestDockerCLI failed with artifacts on master @ 2c0129ce2507e708382cda830d1e47817a299c2e:
Parameters: Same failure on other branches
|
acceptance.TestDockerCLI failed with artifacts on master @ d9cc084baa9892e28fb7211bf715e086170344f5:
Parameters: Same failure on other branches
|
acceptance.TestDockerCLI failed with artifacts on master @ d9cc084baa9892e28fb7211bf715e086170344f5:
Same failure on other branches
|
acceptance.TestDockerCLI failed with artifacts on master @ 7bc721106906327fd58bdaeb41b3831fecef95d2:
Same failure on other branches
|
acceptance.TestDockerCLI failed with artifacts on master @ a6bae227f80c5718b269fa1ec54128f30663c81c:
Same failure on other branches
|
acceptance.TestDockerCLI failed with artifacts on master @ d8ebd299ee910ca93c63206fc6a7d499d5723844:
Same failure on other branches
|
acceptance.TestDockerCLI failed with artifacts on master @ fed5abb731b906c58edbec9c77c0a93b839d7af1:
Same failure on other branches
|
acceptance.TestDockerCLI failed with artifacts on master @ 14f61c5b85b846de91d88108483cb5bce18a7877:
Same failure on other branches
|
I'd say that slow draining of leases is @cockroachdb/kv-distribution |
acceptance.TestDockerCLI failed with artifacts on master @ 93c070a6ee9e9f0ab8aab09bf2f61c7419518455:
Same failure on other branches
|
acceptance.TestDockerCLI failed with artifacts on master @ d49bb7c7d44adb9a6310e010b6b6bad7c7ac5b72:
Same failure on other branches
|
the newest failure is
that seems like it could be a CLI bug. |
acceptance.TestDockerCLI failed with artifacts on master @ 9c5375f6a7375724cdbcbaa0029ed97a230d7abe:
Parameters: Same failure on other branches
|
acceptance.TestDockerCLI failed with artifacts on master @ c0ecd878028c4147a222dae38fb47a1991fd24d2:
Same failure on other branches
|
acceptance.TestDockerCLI failed with artifacts on master @ e872cedf3a5d12e14f584cce02d32e6abf0506dc:
Same failure on other branches
|
acceptance.TestDockerCLI failed with artifacts on master @ c1b01244b9ca995ff078894fd9743ccb9a9b0d3e:
Same failure on other branches
|
acceptance.TestDockerCLI failed with artifacts on master @ 7594fb2d1438dd5ed8f80a887b8d60b6cdd296ed:
Parameters: Same failure on other branches
|
failed again https://teamcity.cockroachdb.com/viewLog.html?buildId=8230212&problemId=4141 opening separate issue for TestDockerCLi/test_sql_mem_monitor flakiness #94887 |
Fixing test_demo_node_cmds.tcl and test_copy.tcl in #94899. The mem monitor is the one that will remain afterwards. |
acceptance.TestDockerCLI failed with artifacts on master @ 90e24ab4313f59fdc825443c03a1f4dc04bcef09:
Same failure on other branches
|
acceptance.TestDockerCLI failed with artifacts on master @ 1fb7236f7b1f53e28bde833c28bed83a976138cf:
Same failure on other branches
|
acceptance.TestDockerCLI failed with artifacts on master @ 639decf058c78f0afe0dba613d60670628c92e81:
Parameters: Same failure on other branches
|
acceptance.TestDockerCLI failed with artifacts on master @ c410d8d740e6943114fcbfde5355e7ba9bfe7c35:
Same failure on other branches
|
acceptance.TestDockerCLI failed with artifacts on master @ 58762ac9e95330e527d79aaf4f5a96c6a7a66231:
Same failure on other branches
|
acceptance.TestDockerCLI failed with artifacts on master @ da247ff22039f4579e2b043656ba561e71876115:
Same failure on other branches
|
acceptance.TestDockerCLI failed with artifacts on master @ 22244a780dcfaca48162dde8e0f90b5ba9b6bb9c:
Same failure on other branches
|
acceptance.TestDockerCLI failed with artifacts on master @ 22244a780dcfaca48162dde8e0f90b5ba9b6bb9c:
Same failure on other branches
|
We have marked this test failure issue as stale because it has been |
acceptance.TestDockerCLI/test_extern_dir.tcl/runMode=docker failed with artifacts on master @ 657c0e14884a7c29cf94192da14ccba699a555aa:
Help
See also: How To Investigate a Go Test Failure (internal)
Parameters in this failure:
This test on roachdash | Improve this report!
Jira issue: CRDB-13132
The text was updated successfully, but these errors were encountered: