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

acceptance: TestDockerCLI failed #77886

Closed
cockroach-teamcity opened this issue Mar 16, 2022 · 3 comments
Closed

acceptance: TestDockerCLI failed #77886

cockroach-teamcity opened this issue Mar 16, 2022 · 3 comments
Assignees
Labels
branch-release-22.1 Used to mark GA and release blockers, technical advisories, and bugs for 22.1 C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. T-server-and-security DB Server & Security

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Mar 16, 2022

acceptance.TestDockerCLI failed with artifacts on release-22.1 @ a1c1879e01ceee79a81693c67a1dba184b5fc1b1:

=== RUN   TestDockerCLI
    test_log_scope.go:79: test logs captured to: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/logTestDockerCLI2376299177
    test_log_scope.go:80: use -show-logs to present logs inline
=== CONT  TestDockerCLI
    cli_test.go:96: -- test log scope end --
test logs left over in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/logTestDockerCLI2376299177
--- FAIL: TestDockerCLI (463.47s)
=== RUN   TestDockerCLI/test_demo_node_cmds.tcl
=== CONT  TestDockerCLI/test_demo_node_cmds.tcl
    cli_test.go:92: non-zero exit code: 1
    --- FAIL: TestDockerCLI/test_demo_node_cmds.tcl (38.03s)
Help

See also: How To Investigate a Go Test Failure (internal)
Parameters in this failure:

  • GOFLAGS=-json

Same failure on other branches

/cc @cockroachdb/sql-experience

This test on roachdash | Improve this report!

Jira issue: CRDB-13811

@cockroach-teamcity cockroach-teamcity added branch-release-22.1 Used to mark GA and release blockers, technical advisories, and bugs for 22.1 C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. labels Mar 16, 2022
@rafiss
Copy link
Collaborator

rafiss commented Mar 16, 2022

[email protected]:26257/movr> \demo restart 3
node 3 has been restarted
[email protected]:26257/movr> select node_id, draining, decommissioning, membe �rship from crdb_internal.gossip_liveness ORDER BY node_id;
  node_id | draining | decommissioning | membership
----------+----------+-----------------+-------------
        1 |  false   |      false      | active
        2 |  false   |      false      | active
        3 |   true   |      false      | active
        4 |  false   |      false      | active
        5 |  false   |      false      | active
(5 rows)


Time: 1ms total (execution 0ms / network 0ms)

[email protected]:26257/movr> 
.220316 05:21:04.944369296 EXPECT TEST: TIMEOUT WAITING FOR "3 |  false   |      false      | active"
non-zero exit code: 1

this is the same error as #76448 and #76391 which it seems that @cameronnunez has been working on.

@blathers-crl blathers-crl bot added the T-server-and-security DB Server & Security label Mar 16, 2022
@cockroach-teamcity
Copy link
Member Author

acceptance.TestDockerCLI failed with artifacts on release-22.1 @ ec0a78bbf61f7d71fe4222cc1c11d262936df2e3:

=== RUN   TestDockerCLI
    test_log_scope.go:79: test logs captured to: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/logTestDockerCLI184642832
    test_log_scope.go:80: use -show-logs to present logs inline
=== CONT  TestDockerCLI
    cli_test.go:96: -- test log scope end --
test logs left over in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/logTestDockerCLI184642832
--- FAIL: TestDockerCLI (610.41s)
=== RUN   TestDockerCLI/test_demo_node_cmds.tcl
=== CONT  TestDockerCLI/test_demo_node_cmds.tcl
    cli_test.go:92: non-zero exit code: 1
    --- FAIL: TestDockerCLI/test_demo_node_cmds.tcl (40.60s)
Help

See also: How To Investigate a Go Test Failure (internal)
Parameters in this failure:

  • GOFLAGS=-json

Same failure on other branches

This test on roachdash | Improve this report!

@shralex
Copy link
Contributor

shralex commented Jun 30, 2023

I'll close this one, because its old and looks to be superseded by #101712

@shralex shralex closed this as completed Jun 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch-release-22.1 Used to mark GA and release blockers, technical advisories, and bugs for 22.1 C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. T-server-and-security DB Server & Security
Projects
None yet
Development

No branches or pull requests

4 participants