stable-25.8: consistently-failing stateless tests with test-only fixes (tracking)

[CarlosFelipeOR]

Type of problem

Tracking issue — stateless tests failing consistently on stable-25.8 whose fix is test-side only (no product bug). Failures that point to a real product limitation are tracked separately (see #2051). All fixes here land in PR #2050; this issue closes when it merges.

Tests

1. 04340_datalake_schema_deep_recursion

• Config: all stateless configs.
• Symptom: expected 'JSONException', got: ... Table function 'deltaLakeLocal'/'icebergLocal' is disabled. Set allow_local_data_lakes to enable it. (SUPPORT_IS_DISABLED).
• Root cause: the test calls deltaLakeLocal/icebergLocal without enabling allow_local_data_lakes, an Altinity-specific guard (default false, added in 25.8.16 Stable: Add guard for local data lakes #1530). The guard fires before the query reaches the JSON parser that would raise the expected JSONException. New test, added in the 25.8.28 bump (PR 25.8 Stable: Bump to 25.8.28 #2024); never passed on this branch.
• Fix: add allow_local_data_lakes=1 to both queries.

2. 04326_parquet_v3_geoparquet_wkb_alloc

• Config: fails only in Stateless tests (amd_ubsan, parallel) (7/7); passes in all other configs.
• Symptom: geo_bomb: UNEXPECTED: — expected MEMORY_LIMIT_EXCEEDED, query completed with no error.
• Root cause: the test asserts that an oversized geometry reserve (100M-point WKB bomb) is charged to max_memory_usage and rejected. In the standalone UBSan build, memory tracking for this allocation isn't reliably enforced (jemalloc is disabled under sanitizers — see note in AllocatorWithMemoryTracking.h), so the limit isn't hit. The DoS fix itself works in production builds. Test is identical in upstream 25.8/master; upstream never builds pure-UBSan (only combined asan_ubsan, where it passes), so this only surfaces in Altinity's CI matrix.
• Fix: add no-ubsan tag.

3. 04409_explain_actions_secret_args and 04410_explain_actions_secret_args_secondary

• Config: fail only in old-analyzer configs (e.g. amd_binary, old analyzer, s3 storage, DatabaseReplicated, parallel), 8/8 each; pass in all other configs (88 OKs each).
• Symptom: Code: 48. EXPLAIN QUERY TREE is only supported with a new analyzer. SET enable_analyzer = 1. (NOT_IMPLEMENTED).
• Root cause: both tests carry the no-old-analyzer tag, but the no-old-analyzer skip support in tests/clickhouse-test was added upstream on master and not backported to 25.8 (present in neither upstream 25.8 nor Altinity stable-25.8). The runner silently ignores the tag, so the tests run under the old analyzer and EXPLAIN QUERY TREE fails. Latent in upstream 25.8 too; only surfaces here because Altinity CI runs an old-analyzer stateless config that upstream 25.8 CI does not.
• Fix: backport the no-old-analyzer handling to tests/clickhouse-test (add FailureReason.OLD_ANALYZER + if "no-old-analyzer" in tags and is_old_analyzer_used(args): return FailureReason.OLD_ANALYZER). Fixes both tests.

Not included here

• 04299_constraint_subst_correlated_subquery_root — real product limitation (correlated subquery + parallel replicas → NOT_IMPLEMENTED). Tracked in stable-25.8: correlated subquery over MergeTree crashes under parallel replicas — Cannot clone ReadFromPreparedSource (NOT_IMPLEMENTED) #2051.