alesapin
af99183950
Disable thread fuzzer after server restart
2022-05-10 15:16:21 +02:00
Alexander Tokmakov
9346c9363a
Merge pull request #37052 from ClickHouse/fix_server_termination_stress_tests
...
Print stacks if we cannot terminate server in stress tests
2022-05-10 13:12:44 +03:00
Alexander Tokmakov
17c954bea7
fix shellcheck
2022-05-10 11:48:55 +02:00
Alexander Tokmakov
92d423c478
print stacks if wa cannot terminate server in stress tests
2022-05-09 19:43:51 +02:00
Alexander Tokmakov
b647f8f9bf
Update run.sh
2022-05-09 17:48:10 +03:00
Alexey Milovidov
419687ac50
Update run.sh
2022-05-09 10:17:49 +02:00
Mikhail f. Shiryaev
b14dca2fac
Improve stress tests report a little bit
2022-05-09 10:17:40 +02:00
Kruglov Pavel
4e2b1cd981
Update run.sh
2022-04-20 16:48:54 +02:00
Kruglov Pavel
cd77f927b6
Fix putting logs into test_output
2022-04-20 15:06:09 +02:00
Kruglov Pavel
6bcdf21801
Fix stress test
2022-04-20 13:53:16 +02:00
Kruglov Pavel
eaad99bd48
Try to turn off always green backward compatibility checks
2022-04-08 13:55:10 +02:00
Kruglov Pavel
9fa6e6e7df
Make backward compatibility check always green
2022-04-07 17:42:33 +02:00
Azat Khuzhin
2fb6d6acb4
stress: use more meaningful names for clickhouse-server.log
...
But note, that stderr.log/stdout.log/clickhouse-server.err.log still not separated.
Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-04-06 14:09:53 +03:00
Azat Khuzhin
058cde820f
test/stress: improve error checks for backward compatiblity check
...
Before the log was analyzed only after the server had been restarted
after stressing, and hence it cannot find anything in case of error,
like here [1].
[1]: https://s3.amazonaws.com/clickhouse-test-reports/34355/acd48ebe2d51d20d0c2a5bc545d46d27f9bf7904/stress_test__thread__actions_.html
Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-04-06 14:09:52 +03:00
Kruglov Pavel
18ab49e788
Check all logs for crashes, logical errors, etc in backward compatibility check
2022-03-25 11:59:50 +01:00
Kruglov Pavel
5efad9699c
Update run.sh
2022-03-23 11:28:40 +01:00
Kruglov Pavel
8ef2f13524
Update run.sh
2022-03-23 11:26:31 +01:00
Kruglov Pavel
034d92d817
Fix removing empty files
2022-03-22 18:06:35 +01:00
avogar
c5245c1ad1
Improve backward compatibility check and stress test
2022-03-22 12:00:20 +00:00
mergify[bot]
5295dd0ef2
Merge branch 'master' into stress-test
2022-03-17 11:10:37 +00:00
Kruglov Pavel
fa6d963f83
Update run.sh
2022-03-16 12:30:45 +01:00
Kruglov Pavel
6b3a25e20d
Update run.sh
2022-03-15 17:15:17 +01:00
avogar
b9496af3b3
Fix tests
2022-03-14 16:40:17 +00:00
Kruglov Pavel
3d36eced2d
Update run.sh
2022-03-10 17:55:45 +03:00
Kruglov Pavel
91b9c11939
Increase the number of attempts to start server
2022-03-10 14:38:39 +03:00
Kruglov Pavel
0f90996bb8
Update run.sh
2022-03-04 14:24:24 +03:00
Kruglov Pavel
8f6ba99fec
Update run.sh
2022-03-01 15:20:02 +03:00
Kruglov Pavel
6252588922
Update run.sh
2022-02-28 13:33:10 +03:00
kssenii
725f967ac6
Add stress test
2022-02-24 07:54:58 +01:00
Kruglov Pavel
500ed56061
Update docker/test/stress/run.sh
...
Co-authored-by: Vladimir C <vdimir@clickhouse.com>
2022-02-18 16:36:48 +03:00
Kruglov Pavel
10c45bef67
Remove clickhouse-test package
2022-02-18 13:03:23 +03:00
Kruglov Pavel
74087470c2
Update run.sh
2022-02-18 12:52:56 +03:00
Kruglov Pavel
e77319bf01
Merge branch 'master' into stress-test
2022-02-17 20:28:46 +03:00
Yatsishin Ilya
bbe2c07a7b
remove clickhouse-test deb completely
2022-02-15 12:03:51 +00:00
Azat Khuzhin
4965586e7e
More gdb introspection on CI ( #34517 )
...
* test/fuzzer: preserve core
This may help to capture things like in [1]:
Failed assertion: "bin->low_bits_full > bin->low_bits_empty" Received signal 6 Received signal Aborted (6)
[1]: https://s3.amazonaws.com/clickhouse-test-reports/33057/19216f4c0ae0f72108c147f958a708b521ad27dc/fuzzer_astfuzzerdebug,actions//report.html
Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
* test: do not run 'info locals' since 'backtrace full' includes it
Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
* test: try capture backtrace from all threads
Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
* test/stress: fix path for core artifacts
Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
Fixes : #33389
* test/fuzzer: store core file in artifacts
v2: fix report, because of undefined variable CORE_LINK
v3: fix case when there is no core file
Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-02-13 15:02:15 +03:00
Kruglov Pavel
e004dae25b
Update run.sh
2022-01-27 18:15:03 +03:00
Kruglov Pavel
b54bf18b27
Merge branch 'master' into stress-test
2022-01-25 14:35:42 +03:00
Kruglov Pavel
d5bde26bc1
Update run.sh
2022-01-20 15:22:00 +03:00
Azat Khuzhin
ebed6193b4
tests/stress: add core dumps into artifacts
...
gcore is used here because:
- default kernel.core_pattern is "|/usr/share/apport/apport %p %s %c %d %P %E" [1]
and so to make it work you need to install apport into container and
configure it propertly -- to complex
[1]: https://s3.amazonaws.com/clickhouse-test-reports/33389/204e459d259570e6bc7fe2903f7e516094a916ca/stress_test__address__actions_/runlog.log
- kernel.core_pattern cannot be changed, since proc is mounted in
read-only mode in non --privileged containers [2]
[2]: https://s3.amazonaws.com/clickhouse-test-reports/33389/dab3afbd94558f9654bf0aa1e06e06e2962f3bb0/stress_test__address__actions_/runlog.log
v2: change kernel.core_pattern
v3: use gcore, since you are not allowed to change kernel.core_pattern
in container (only under --privileged)
2022-01-04 14:03:40 +03:00
Kruglov Pavel
ffb6c5b37b
Merge branch 'master' into stress-test
2021-12-23 20:14:15 +03:00
Alexander Tokmakov
bd5931e5af
improve gdb script
2021-12-15 13:21:21 +03:00
Alexander Tokmakov
dfa31a6577
fix
2021-12-10 22:38:34 +03:00
tavplubix
5079134ffd
Update run.sh
2021-12-10 20:10:49 +03:00
Alexander Tokmakov
254d6c5d59
fix
2021-12-10 20:07:28 +03:00
Alexander Tokmakov
3ff8aff1b5
try to fix attaching gdb
2021-12-10 18:03:57 +03:00
tavplubix
85e53b1b1f
Try fix attaching gdb in tests ( #32448 )
...
* attach gdb with sudo
* fix
* Update run.sh
2021-12-10 00:12:45 +03:00
Azat Khuzhin
f8bf3b1993
stress: use max_memory_usage_for_user as a soft limit to avoid memory limit exceeded
...
By using max_memory_usage_for_user as a soft limit, and after
max_server_memory_usage as a hard, we can allow normal overcommit, using
max_memory_usage_for_user=0 instead of relying on max_untracked_memory.
2021-12-06 09:05:34 +03:00
mergify[bot]
b4f43c59a2
Merge branch 'master' into stress-test
2021-12-01 10:12:22 +00:00
alesapin
b4d4295c16
Followup
2021-11-30 13:24:04 +03:00
alesapin
085a30b98e
Fixup
2021-11-30 13:22:50 +03:00