Skip to content

Stable 26.8 - CICD Continued - #2581

Open
strtgbb wants to merge 7 commits into
stable-26.8from
cicd/stable-26.8/continued
Open

strtgbb wants to merge 7 commits into
stable-26.8from
cicd/stable-26.8/continued

Conversation

@strtgbb

@strtgbb strtgbb commented Oct 15, 2026

Copy link
Copy Markdown
Collaborator

CICD Fixes and ports for 26.8

Changelog category (leave one):

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

CI/CD Options

Exclude tests:

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

Regression jobs to run:

  • Fast suites (mostly <1h)
  • Aggregate Functions (2h)
  • Alter (1.5h)
  • Benchmark (30m)
  • CAS (content-addressed storage; Antalya only)
  • ClickHouse Keeper (1h)
  • Iceberg (2h)
  • LDAP (1h)
  • OAuth (5m)
  • Parquet (1.5h)
  • RBAC (1.5h)
  • SSL Server (1h)
  • S3 (2h)
  • S3 Export (2h)
  • Swarms (30m)
  • Tiered Storage (2h)

strtgbb and others added 7 commits October 15, 2026 13:44
ARM sanitizer builds disable SimSIMD so `02354_vector_search_rescoring_distance_in_select_list` disagrees with the binary-build reference.

Co-authored-by: Cursor <cursoragent@cursor.com>
Commit statuses belong to the commit, not the ref. When a release tag points at
the tip of its branch, the branch run and the tag run write to the same job
names, and `get_commit_statuses` kept whichever was newest. The jobs table then
showed failures from the branch run while the error tables, which filter on the
tag, did not.

For release runs, keep only statuses whose results link has the reported ref in
it (`REF=<ref>&` or `/REFs/<ref>/`). Pull request runs are not filtered.

Report: https://s3.amazonaws.com/altinity-build-artifacts/REFs/v26.6.8.20002.altinityantalya/20d68b0d4aea62a8977f154edd004e553fc5d034/38626451129/ci_run_report.html#ci-jobs-status

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The search link used `merged:>YYYY-MM-DD`, which GitHub reads as strictly after
that whole day. PRs merged later on the baseline day were left out, such as
#2315 and #2529 for 26.6.8.20002. The date also came from the release publish
time, while the table lists PRs after the baseline tag commit.

Use the UTC commit time of the baseline commit for both baseline sources, so
`merged:>` matches the range used for the table and the version bump PR that
created the baseline is excluded.

Report: https://s3.amazonaws.com/altinity-build-artifacts/REFs/v26.6.8.20002.altinityantalya/20d68b0d4aea62a8977f154edd004e553fc5d034/38626451129/ci_run_report.html#prs-in-release

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@strtgbb strtgbb added cicd Improvements and fixes to the CICD process 26.8 labels Oct 15, 2026
@github-actions

Copy link
Copy Markdown

Workflow [PR], commit [1791d7a]

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

26.8 cicd Improvements and fixes to the CICD process

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant