ClickHouse/tests/queries/0_stateless/02050_client_profile_events.reference

0
100000
[ 0 ] SelectedRows: 131010 (increment)
OK
OK
client: add ability to print raw profile events This can be useful for debugging and for testing (since you will not need to obtain query_id and look at query_log). v2: - mark test as long - add option to docs - add type of profile event into logs too v3: - resolve conflicts - and fix onProfileEvents callback v4: - add --print-profile-events separate switch 2021-10-12 18:03:54 +00:00			`0`
tests: add more information for 02050_client_profile_events in case of failure Sometimes [1] the test fails like this: 2021-12-10 03:41:19 --- /usr/share/clickhouse-test/queries/0_stateless/02050_client_profile_events.reference 2021-12-10 03:23:43.000000000 -0500 2021-12-10 03:41:19 +++ /tmp/clickhouse-test/0_stateless/02050_client_profile_events.617.stdout 2021-12-10 03:41:19.509611205 -0500 2021-12-10 03:41:19 @@ -1,4 +1,3 @@ 2021-12-10 03:41:19 0 2021-12-10 03:41:19 -SelectedRows: 131010 (increment) 2021-12-10 03:41:19 OK 2021-12-10 03:41:19 OK 2021-12-10 03:41:19 2021-12-10 03:41:19 2021-12-10 03:41:19 Database: test_73d5o0 [1]: https://s3.amazonaws.com/clickhouse-test-reports/32493/703213a6444f8014e3324df4b6e44d03fa351294/stateless_tests_flaky_check__address__actions_.html And I did not find anything strange in server logs (and there was 0 exceptions). 2021-12-14 07:25:30 +00:00			`100000`
tests: add thread_id into 02050_client_profile_events 2021-12-14 07:25:30 +00:00			`[ 0 ] SelectedRows: 131010 (increment)`
client: add ability to print raw profile events This can be useful for debugging and for testing (since you will not need to obtain query_id and look at query_log). v2: - mark test as long - add option to docs - add type of profile event into logs too v3: - resolve conflicts - and fix onProfileEvents callback v4: - add --print-profile-events separate switch 2021-10-12 18:03:54 +00:00			`OK`
			`OK`