Commit Graph

16 Commits

Author SHA1 Message Date
Pablo Marcos
7965c5dd34 Merge branch 'master' into system-query-metric-log 2024-09-30 07:56:32 +00:00
robot-clickhouse
7c6ce8611c Automatic style fix 2024-09-27 10:19:49 +00:00
Pablo Marcos
a561899da0 Rename system.query_log_metric to system.query_metric_log
Seems I had at the very beginning a brainfart and started using
query_log_metric instead of query_metric_log and it went on and on
:facepalm
2024-07-19 14:13:15 +00:00
Pablo Marcos
639383b7a1 Fix configs for query_log_metric 2024-07-19 13:21:33 +00:00
Pablo Marcos
216d26987a Add test and config changes for system.error_log 2024-06-18 08:37:40 +00:00
Alexander Tokmakov
bcec53aadc Merge branch 'master' into mvcc_prototype 2022-03-23 11:28:43 +01:00
Mikhail f. Shiryaev
e6f5a3f98b
Apply black formatter to all *.py files in the repo 2022-03-22 17:39:58 +01:00
Alexander Tokmakov
e1a41fc694 add system log for introspection 2022-01-14 17:03:00 +03:00
Azat Khuzhin
d030e08d05 Make test_MemoryTracking::test_http not flaky
By comparing only megabytes in the memory changes, instead of bytes as
before, since it may be tricky at least due to max_untracked_memory and
how thread pool handle it.

It should be safe, since originally it was written in #16121 which fixes
issue #15932, which has ~4MB consumption of memory per request.
2021-10-14 21:06:39 +03:00
Azat Khuzhin
56ab0e31e6 Add description for test_MemoryTracking 2021-10-14 21:06:22 +03:00
Alexey Milovidov
e513a5db32 Change <yandex> to <clickhouse> in configs 2021-09-20 01:38:53 +03:00
Nikita Mikhaylov
2b59fbacd3
Update tests/integration/test_MemoryTracking/test.py 2021-09-08 16:14:00 +03:00
Azat Khuzhin
e5d7791f87 Fix test_MemoryTracking integration test flakiness 2021-09-08 09:36:51 +03:00
Yatsishin Ilya
06bb4e2c71 wip 2021-03-16 13:00:49 +03:00
Azat Khuzhin
96da5f6534 Disable syncing MemoryTracking with RSS for test_MemoryTracking 2020-10-24 02:33:16 +03:00
Azat Khuzhin
6e5b04fad8 Make 01540_MemoryTracking integration
01540_MemoryTracking is failing on CI for the following reasons:
- log_queries (fixed, by adding log_queries=0)
- profilers (fixed)
- but what can't be fixed is metric_log and so on, so we need separate
  instance with separate configuration (sigh).
2020-10-24 02:27:29 +03:00