thevar1able/ClickHouse
1
0
Fork 0
mirror of https://github.com/ClickHouse/ClickHouse.git synced 2024-11-28 02:21:59 +00:00
Code Issues Packages Projects Releases Wiki Activity
89,218 Commits 9,188 Branches 1,782 Tags 2.2 GiB
78069765bb
Commit Graph

118 Commits

Author SHA1 Message Date
kssenii
d59d4eda4f Fix tests 2022-04-06 01:58:16 +02:00
alesapin
b838a7dcb0 Remove outdated links from CI 2022-03-28 15:53:22 +02: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
alesapin
333dfab6a6 Add retries to AST fuzzer 2021-12-28 16:12:51 +03:00
alesapin
118004015a Longer timeout for server start in fuzzer 2021-12-24 14:56:51 +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
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
Kruglov Pavel
ef42cd6821
Merge pull request #32138 from Avogar/fix-apply-lambda 
Fix 'APPLY lambda' parsing
 2021-12-09 17:09:11 +03:00
tavplubix
f4cbbfd8c0
Update run-fuzzer.sh 2021-12-09 14:17:55 +03:00
tavplubix
de0a9a84a9
Update run-fuzzer.sh 2021-12-09 13:51:39 +03:00
Kruglov Pavel
1df2383d00
Update run-fuzzer.sh 2021-12-09 12:17:31 +03:00
avogar
51bb37715f Fix fuzzer 2021-12-08 21:29:50 +03:00
alesapin
5815429059 Shorter stress and fuzzer tests 2021-11-25 17:54:50 +03:00
Azat Khuzhin
40be97c1dd Improve fuzzer report in case of fuzzer killed 
This will avoid Exception from fuzzer in description like in [1], that
someone may think that is related to the failure, which is obviously
don't in case it was KILLed.

  [1]: https://clickhouse-test-reports.s3.yandex.net/31259/a49e10c78860a451ff9cc39df6049c88234d507a/fuzzer_ubsan/report.html#fail1
 2021-11-12 01:01:10 +03:00
alesapin
4eca493ab8 Fix fuzzer on master 2021-10-29 13:47:29 +03:00
alesapin
ffc8dbd085
Update run-fuzzer.sh 2021-10-28 23:06:04 +03:00
alesapin
313584e553
Update run-fuzzer.sh 2021-10-28 19:12:47 +03:00
alesapin
0651a1f0e9
Update run-fuzzer.sh 2021-10-28 17:03:40 +03:00
alesapin
542196128b Trying to make fuzzer check less hardcoded 2021-10-28 12:29:50 +03:00
Azat Khuzhin
aeb670dbe0 Simplify obtaining of server pid in fuzzer tests 2021-10-05 21:05:49 +03:00
Nikita Mikhaylov
731d6c5755
Merge pull request #29513 from azat/fuzzer-fix-server-pid 
Fix server pid (hence exit code and attaching with gdb) in fuzzer tests
 2021-10-04 19:59:24 +03:00
Azat Khuzhin
74a7a0603d test/fuzzer: print stacktrace 
To get the stacktrace for errors w/o it [1]:

    SET max_parser_depth = 4000

    Got boring AST
    Code: 306. DB::Exception: Maximum parse depth (1000) exceeded. Consider rising max_parser_depth parameter. (TOO_DEEP_RECURSION)

  [1]: https://clickhouse-test-reports.s3.yandex.net/29513/769bfbe71f22c392458eced655080a0bbd442e02/fuzzer_ubsan/fuzzer.log
 2021-10-02 12:49:44 +03:00
Azat Khuzhin
769bfbe71f Fix server pid in fuzzer tests 
Previously it was the pid of the subshell 40 while it should be the pid
of the clickhouse-server 39:

Here we see that the server pid is 39:

    2021-09-28 11:02:34	 + pgrep -f clickhouse-server
    2021-09-28 11:02:34	 39

Here we see that the 40 is the pid of subshell:

    2021-09-28 11:02:45	 ch/docker/test/fuzzer/run-fuzzer.sh: line 90:    39 Killed                  clickhouse-server --config-file db/config.xml -- --path db 2>&1
    2021-09-28 11:02:45	         40 Done                    | tail -100000 > server.log

And here we see that server_pid variable is 40:

    2021-09-28 11:02:45	 + server_exit_code=0
    2021-09-28 11:02:45	 + wait 40

v2: wait in background to call wait in foreground and ensure that the
process is alive, since w/o job control this is the only way to obtain
the exit code
 2021-10-01 21:05:30 +03:00
Sergei Semin
b739d1cc92 make changes analog to https://github.com/ClickHouse/ClickHouse/pull/20495/files but for clang-13 2021-09-09 23:51:47 +03:00
mergify[bot]
6ccf905133
Merge branch 'master' into try-llvm-12 2021-09-03 16:13:13 +00:00
Vladimir C
4cbc1aba19
Disable SC2001 shellcheck in docker/test/fuzzer/run-fuzzer.sh 2021-08-31 11:02:52 +03:00
vdimir
bc785bff25
Fix sed argument in test/fuzzer/run-fuzzer.sh 2021-08-30 14:25:08 +03:00
Ilya Yatsishin
7f7ecb0c60
Merge branch 'master' into try-llvm-12 2021-08-26 18:58:49 +03:00
vdimir
92f073a435
Call generate-test-j2.py in run-fuzzer.sh before calculating NEW_TESTS_OPT 2021-08-25 16:05:16 +03:00
vdimir
0e37203dcd
Use jinja template tests in fuzzer 2021-08-25 11:18:30 +03:00
mergify[bot]
bde834a8c0
Merge branch 'master' into try-llvm-12 2021-08-19 18:21:29 +00:00
Alexander Kuzmenkov
1f48166bfb
Update run-fuzzer.sh 2021-08-16 16:55:20 +03:00
Yatsishin Ilya
9145dd3fd0 Merge branch 'master' into try-llvm-12 2021-08-06 19:14:01 +03:00
Alexander Kuzmenkov
dbf0ed31e8 record server exit code in fuzzer 2021-07-22 17:05:47 +03:00
Azat Khuzhin
f00a4668a4 Set follow-fork-mode child for gdb in stress/fasttest/fuzzer 
Sometimes gdb does not catch SIGSEGV [1], let's try set this setting,
since maybe some code from contrib does fork.

  [1]: https://clickhouse-test-reports.s3.yandex.net/25605/cd5a3c8d7eb417f6df211b4507dc970933f8549a/stress_test_(thread).html#fail1
 2021-06-28 10:04:08 +03:00
Alexey Milovidov
7aacca94e3 Fix error in Fuzzer (CC @akuzm) 2021-06-17 09:16:34 +03:00
Yatsishin Ilya
46023c4b99 merge remote-tracking branch 'origin' into try-llvm-12 2021-06-03 15:32:22 +03:00
Alexander Kuzmenkov
23e66243e7 more fuzzer fixes... 2021-06-02 21:45:07 +03:00
Alexander Kuzmenkov
34509b26ba another fuzzer fix 2021-06-02 18:57:01 +03:00
Alexander Kuzmenkov
78fe7891b4 better messages in fuzzer status 2021-06-02 15:06:12 +03:00
Alexander Kuzmenkov
104f9bf6de Merge remote-tracking branch 'origin/master' into HEAD 2021-05-29 16:12:34 +03:00
Alexander Kuzmenkov
73c2ca7da5 fixes 2021-05-29 16:12:18 +03:00
Alexander Kuzmenkov
2116d0d53d
Update run-fuzzer.sh 2021-05-29 01:57:16 +03:00
Alexander Kuzmenkov
d33480ce84 fix failing grep 2021-05-28 20:47:06 +03:00
Alexander Kuzmenkov
1f1a77438b more fuzzer fixes 2021-05-28 15:55:58 +03:00
Alexander Kuzmenkov
81d9c9ee30
Update docker/test/fuzzer/run-fuzzer.sh 
Co-authored-by: Azat Khuzhin <a3at.mail@gmail.com>
 2021-05-28 13:05:02 +03:00
Alexander Kuzmenkov
ee71db564a ast fuzzer: determine server death more robustly 2021-05-27 21:26:47 +03:00