Antalya 25.8 - Move stateless crossout logic into clickhouse-test

[strtgbb]

Changelog category (leave one):

• CI Fix or Improvement (changelog entry is not required)

Moving the crossout logic into clickhouse-test allows for the broken tests list to function locally and show BROKEN status in actions logs.

Added a new clickhouse-test argument --known-fails-file-path

This PR is required for #1185

CI/CD Options

Exclude tests:

• Fast test
• Integration Tests
• Stateless tests
• Stateful tests
• Performance tests
• All with ASAN
• All with TSAN
• All with MSAN
• All with UBSAN
• All with Coverage
• All with Aarch64
• All Regression
• Disable CI Cache

Regression jobs to run:

• Fast suites (mostly <1h)
• Aggregate Functions (2h)
• Alter (1.5h)
• Benchmark (30m)
• ClickHouse Keeper (1h)
• Iceberg (2h)
• LDAP (1h)
• Parquet (1.5h)
• RBAC (1.5h)
• SSL Server (1h)
• S3 (2h)
• Tiered Storage (2h)

[github-actions]

Workflow [PR], commit [8775858]

[strtgbb]

Crossouts are still not working reliably when the match message is on the first line.

The first line in the praktika report is created from both reason and description, which are not merged at the point that the crossout logic runs.

The crossout logic cannot be moved to after the merge happens, because the test status must be set before then.

[CarlosFelipeOR]

Test Plan – PR #1227

Objective

Verify that known broken tests are marked as BROKEN by clickhouse-test (locally and in CI), including newly added entries in tests/broken_tests.yaml.

---

1️⃣ Local execution (core change)

• Run stateless tests locally using the standard runner (Praktika)
• Confirm tests listed in tests/broken_tests.yaml are marked as BROKEN (not FAIL)
• Confirm at least one known failing test not in broken_tests.yaml remains FAIL.
• Confirm broken_tests_handler.log is generated when BROKEN rules apply

---

2️⃣ Newly added broken tests (Azure filesystem cache)

These tests fail locally and in contributor CI when Azure storage is not configured, and should be marked as BROKEN when the Azure-related error occurs.

• 02313_filesystem_cache_seeks
• 02286_drop_filesystem_cache
• 02242_system_filesystem_cache_log_table
• 02241_filesystem_cache_on_write_operations
• 02240_system_filesystem_cache_table
• 02226_filesystem_cache_profile_events

---

3️⃣ CI validation

• Confirm known broken tests are reported as BROKEN in CI logs and test reports
• (If applicable) In sanitizer CI jobs (e.g. ASAN/TSAN), verify whether any process group timeout failures are classified as BROKEN
• Ensure no unexpected regressions or CI failures are introduced

---

✅ Acceptance criteria

• Known broken tests are consistently marked as BROKEN locally and in CI
• Newly added Azure-related broken tests behave as expected

[strtgbb]

The aforementioned issue has been resolved, see 03357_join_pk_sharding here:
https://altinity-build-artifacts.s3.amazonaws.com/json.html?PR=1227&sha=87758587f2602eb85cd42c1e41c7812ea7e17aa8&name_0=PR&name_1=Stateless+tests+%28amd_tsan%2C+s3+storage%2C+parallel%29&name_1=Stateless+tests+%28amd_tsan%2C+s3+storage%2C+parallel%29&name_2=Tests