thevar1able/ClickHouse
1
0
Fork 0
mirror of https://github.com/ClickHouse/ClickHouse.git synced 2024-12-15 10:52:30 +00:00
Code Issues Packages Projects Releases Wiki Activity
2602c39649
ClickHouse/tests/queries/0_stateless/02116_interactive_hello.expect

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

34 lines
1.0 KiB
Plaintext
Raw Normal View History

Add test
2021-11-14 07:57:02 +00:00
#!/usr/bin/expect -f
Add exp_internal for expect tests This is to catch possible issues like 01565_reconnect_after_client_error in [1]. [1]: https://s3.amazonaws.com/clickhouse-test-reports/38417/e33f236d502fe9f7906392f4ceffaee44e3c4ce4/stateless_tests__thread__actions__[3/3].html Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-07-02 09:05:52 +00:00
set basedir [file dirname $argv0]
set basename [file tail $argv0]
Better usability of "expect" tests: less trouble with running directly
2024-03-23 16:52:26 +00:00
if {[info exists env(CLICKHOUSE_TMP)]} {
set CLICKHOUSE_TMP $env(CLICKHOUSE_TMP)
} else {
set CLICKHOUSE_TMP "."
}
exp_internal -f $CLICKHOUSE_TMP/$basename.debuglog 0
set history_file $CLICKHOUSE_TMP/$basename.history
Add exp_internal for expect tests This is to catch possible issues like 01565_reconnect_after_client_error in [1]. [1]: https://s3.amazonaws.com/clickhouse-test-reports/38417/e33f236d502fe9f7906392f4ceffaee44e3c4ce4/stateless_tests__thread__actions__[3/3].html Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-07-02 09:05:52 +00:00
Add test
2021-11-14 07:57:02 +00:00
log_user 0
set timeout 60
match_max 100000
expect_after {
Do not ignore eof in expect tests expect_after that adjusts default timeout handler, reseted eof handler, and this tell expect that it can ignore eof from read, consider the following example: <details> ```expect #!/usr/bin/expect -f exp_internal 1 log_user 1 set timeout 4 match_max 100000 expect_after { # eof { exp_continue } timeout { exit 1 } } spawn bash -c "sleep 1; echo ':) '" expect ":) " ``` ``` $ ./expect.expect < /dev/null spawn bash -c sleep 1; echo ':) ' parent: waiting for sync byte parent: telling child to go ahead parent: now unsynchronized from child spawn: returns {6614} expect: does "" (spawn_id exp4) match glob pattern ":) "? no expect: read eof ^^^ expect: set expect_out(spawn_id) "exp0" expect: set expect_out(buffer) "" ``` And with uncommented eof handler: ``` $ ./expect.expect < /dev/null spawn bash -c sleep 1; echo ':) ' parent: waiting for sync byte parent: telling child to go ahead parent: now unsynchronized from child spawn: returns {17959} expect: does "" (spawn_id exp4) match glob pattern ":) "? no expect: read eof expect: set expect_out(spawn_id) "exp0" expect: set expect_out(buffer) "" expect: continuing expect after update expect: does "" (spawn_id exp4) match glob pattern ":) "? no expect: does ":) \r\n" (spawn_id exp4) match glob pattern ":) "? yes expect: set expect_out(0,string) ":) " expect: set expect_out(spawn_id) "exp4" expect: set expect_out(buffer) ":) " ``` </details>
2021-12-28 18:16:04 +00:00
# Do not ignore eof from expect
Fix timeout for expect tests by fixing expect_after timeout By default expect matches patterns against output from the current process, however if you don't have stdin attached (like the case for CI), you will not have anything to check against, hence "timeout" simply does not work. Likely expect has $any_spawn_id (another option is to put expect_after after spawn). v2: use $any_spawn_id Refs: https://github.com/ClickHouse/ClickHouse/pull/43819 Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-02-20 14:50:15 +00:00
-i $any_spawn_id eof { exp_continue }
Do not ignore eof in expect tests expect_after that adjusts default timeout handler, reseted eof handler, and this tell expect that it can ignore eof from read, consider the following example: <details> ```expect #!/usr/bin/expect -f exp_internal 1 log_user 1 set timeout 4 match_max 100000 expect_after { # eof { exp_continue } timeout { exit 1 } } spawn bash -c "sleep 1; echo ':) '" expect ":) " ``` ``` $ ./expect.expect < /dev/null spawn bash -c sleep 1; echo ':) ' parent: waiting for sync byte parent: telling child to go ahead parent: now unsynchronized from child spawn: returns {6614} expect: does "" (spawn_id exp4) match glob pattern ":) "? no expect: read eof ^^^ expect: set expect_out(spawn_id) "exp0" expect: set expect_out(buffer) "" ``` And with uncommented eof handler: ``` $ ./expect.expect < /dev/null spawn bash -c sleep 1; echo ':) ' parent: waiting for sync byte parent: telling child to go ahead parent: now unsynchronized from child spawn: returns {17959} expect: does "" (spawn_id exp4) match glob pattern ":) "? no expect: read eof expect: set expect_out(spawn_id) "exp0" expect: set expect_out(buffer) "" expect: continuing expect after update expect: does "" (spawn_id exp4) match glob pattern ":) "? no expect: does ":) \r\n" (spawn_id exp4) match glob pattern ":) "? yes expect: set expect_out(0,string) ":) " expect: set expect_out(spawn_id) "exp4" expect: set expect_out(buffer) ":) " ``` </details>
2021-12-28 18:16:04 +00:00
# A default timeout action is to do nothing, change it to fail
Fix timeout for expect tests by fixing expect_after timeout By default expect matches patterns against output from the current process, however if you don't have stdin attached (like the case for CI), you will not have anything to check against, hence "timeout" simply does not work. Likely expect has $any_spawn_id (another option is to put expect_after after spawn). v2: use $any_spawn_id Refs: https://github.com/ClickHouse/ClickHouse/pull/43819 Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-02-20 14:50:15 +00:00
-i $any_spawn_id timeout { exit 1 }
Add test
2021-11-14 07:57:02 +00:00
}
One cannot use /dev/null as a history file since replxx run chmod Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-02-20 12:55:42 +00:00
spawn bash -c "source $basedir/../shell_config.sh ; \$CLICKHOUSE_CLIENT_BINARY \$CLICKHOUSE_CLIENT_OPT --disable_suggestion --history_file=$history_file"
Add test
2021-11-14 07:57:02 +00:00
tests: fix 02116_interactive_hello for "official build" Example of such greeting: 2023-02-26 15:26:33 expect: does "\u001b[0J\u001b[?25hClickHouse client version 23.3.1.207 (official build).\r\nConnecting to database test_i4r0kozg at localhost:9000 as user default.\r\nConnected to ClickHouse server version 23.3.1 revision 54461.\r\n\r\nWarnings:\r\n * Server logging level is set to 'test' and performance is degraded. This cannot be used in production.\r\n * Linux is not using a fast clock source. Performance can be degraded. Check /sys/devices/system/clocksource/clocksource0/current_clocksource\r\n * The setting 'allow_remote_fs_zero_copy_replication' is enabled for MergeTree tables. But the feature of 'zero-copy replication' is under development and is not ready for production. The usage of this feature can lead to data corruption and loss. The setting should be disabled in production.\r\n * Table system.session_log is enabled. It's unreliable and may contain garbage. Do not use it for any kind of security monitoring.\r\n\r\n\u001b[?2004h\u001b[1Gfunctional-tests :) " (spawn_id exp4) match regular expression "ClickHouse client version [\d]{2}.[\d]{1,2}.[\d]{1,2}.[\d]{1,}.\r"? Gate "ClickHouse client version *\r"? gate=yes re=no CI: https://s3.amazonaws.com/clickhouse-test-reports/0/df1e18ad4cb9b08240273169ca7dd6ca1cac617c/stateless_tests__aarch64_/run.log Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2023-02-26 06:35:38 +00:00
# (?n) - Do not match new lines
expect -re "(?n)ClickHouse client version \[\\d\]{2}\.\[\\d\]{1,2}\.\[\\d\]{1,2}\.\[\\d\]{1,}.*\r"
expect -re "(?n)Connecting to database .* at localhost:9000 as user default\.\r"
Don't print server revision in client on connect (#57435)
2023-12-02 15:32:34 +00:00
expect -re "(?n)Connected to ClickHouse server version \[\\d\]{2}\.\[\\d\]{1,2}\.\[\\d\]{1,2}\.\r"
Add test
2021-11-14 07:57:02 +00:00
expect ":) "
send -- ""
expect eof
Reference in New Issue Copy Permalink