Cherry-pick: Backport #83607 to 24.8: Fix incorrect memory around max_untracked_memory - #2087
Conversation
Backport ClickHouse#83607 to 24.8: Fix incorrect memory around max_untracked_memory
|
This is an automated comment for commit e3dc01e with description of existing statuses. It's updated for the latest CI running ❌ Click here to open a full report in a separate page
Successful checks
|
CI triage — 2 failing checks: 0 PR-caused (code), 1 process (DCO), 1 infra timeoutGood news up front: this is a clean, faithful backport and no test actually failed. Both red checks are non-code issues. The change ( 1. DCO — ❌ fail → PR-related (metadata, not code)The head commit This is the usual DCO trip for commits lifted from upstream. It's not a code problem and won't affect correctness. Fix (needs a history rewrite / force-push, so it has to be done by you — I'm not permitted to force-push): git checkout releasy/port/pr-83715-a3a46e
git rebase --signoff customizations/24.8.14
git push --force-with-lease
2. Integration tests (release) [2/4] — ❌ fail → infra/timeout, NOT PR-causedCheck summary: Fix: just re-run that one job — safe to re-run.
Bottom line: nothing here blocks merge on technical grounds. Add the sign-off (or override DCO) and re-run the timed-out integration shard, and CI should go green. |
Cherry-picked from ClickHouse#83715.
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes into CHANGELOG.md):
Fix incorrect memory around max_untracked_memory (ClickHouse#83607 by @azat)
CI/CD Options
Exclude tests:
Regression jobs to run: