acceptance: TestDockerCLI_test_copy failed

[cockroach-teamcity]

acceptance.TestDockerCLI_test_copy failed with artifacts on release-23.2 @ e6f2550b85be0dff1591247a1085bb26d1411f4b:

=== RUN   TestDockerCLI_test_copy
    test_log_scope.go:170: test logs captured to: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/_tmp/ba7bd39f117af684bba3ca6bf23662ce/logTestDockerCLI_test_copy2229450715
    test_log_scope.go:81: use -show-logs to present logs inline
    generated_cli_test.go:89: -- test log scope end --
test logs left over in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/_tmp/ba7bd39f117af684bba3ca6bf23662ce/logTestDockerCLI_test_copy2229450715
--- FAIL: TestDockerCLI_test_copy (66.85s)
=== RUN   TestDockerCLI_test_copy/test_copy.tcl
    util_docker.go:257: non-zero exit code: 1
    --- FAIL: TestDockerCLI_test_copy/test_copy.tcl (56.61s)

Help

See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)

/cc @cockroachdb/sql-foundations

This test on roachdash | Improve this report!

Jira issue: CRDB-34132

[rafiss]

This is an issue with the CLI prompt.

\copy t FROM STDIN CSV;
Enter data to be copied followed by a newline.
End with a backslash and a period on a line by itself, or an EOF signal.
expect: does "localhost:26257/defaultdb> \copy t FROM STDIN CSV;\r\nEnter data to be copied followed by a newline.\r\nEnd with a backslash and a period on a line by itself, or an EOF signal.\r\n" (spawn_id exp3) match glob pattern ">>"? no
expect: timed out

.231205 17:37:28.116780724 EXPECT TEST: TIMEOUT WAITING FOR ">>"

[rafiss]

We will prioritize this if it happens more frequently.

[yuzefovich]

Re-opening since this was incorrectly closed by exalate. Also lowering this to P-3 since it seems relatively rare.

[github-actions[bot]]

We have marked this test failure issue as stale because it has been inactive for 1 month. If this failure is still relevant, removing the stale label or adding a comment will keep it active. Otherwise, we'll close it in 5 days to keep the test failure queue tidy.