Repository navigation
Antalya 26.8 - Port CICD fixes from stable 26.8 - #2633
Merged
Merged
Conversation
…ct_list` so ARM sanitizer builds match after SimSIMD was disabled. USearch's SimSIMD kernels and its scalar fallback disagree in the last bits (0.203125 vs 0.1875). Neighbor order is unchanged. https: //github.com/Altinity/ClickHouse/actions/runs/35220699056 https: //github.com//pull/2358 Co-authored-by: Cursor <cursoragent@cursor.com>
Release v26.8.7.19-lts
The tool filtered for `clickhouse-gh[bot]` and path-style S3 URLs, so PR fetches missed the `github-actions[bot]` comment and never printed `--failed` details from the workflow report. Co-authored-by: Cursor <cursoragent@cursor.com>
Release v26.8.9.10-lts
Release v26.8.10.6-lts
Release v26.8.11.7-lts
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>
Stable 26.8 - Report: Speed up prs table data fetch
strtgbb
added
cicd
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ports CI fixes from stable 26.8 onto
antalya-26.8.Related: #2581
Workflow report
A release report on a tag showed failures from the branch run. The tag and the branch share a commit and write the same job names, and the report kept whichever status was newest. A release report on a tag now keeps a status only when its results link contains that ref (
REF=<ref>&for Praktika jobs,/REFs/<ref>/for regression jobs). A pull request report still lists every status on the commit. Two branch runs on the same commit can still overwrite each other.The "PRs in release" link missed pull requests merged later on the baseline day. GitHub treats a date-only
merged:>YYYY-MM-DDas the start of the next day. The link now uses the baseline commit's UTC time (merged:>YYYY-MM-DDTHH:MM:SSZ), so the version-bump pull request that created the baseline stays out of the table.Building the PRs table fetched a deep git history, and a shallow checkout often could not see the baseline. The fetch process has now been properly optimized
Related: #2580
Related: #2618
CI jobs
${{ github.workflow }}-${{ github.ref }}on Fast Builds, MasterCI, PR, and community PR, so each ref proceeds on its own.parser_memory_check, which fails on Altinity pull requests. It looks up masterclickhouse-exampleson upstream S3.Related: #2476
Related: #2618
Images
alpine:3.21base. The image now usesFROM alpineand runs a fullapk upgrade.Related: #2476
Related: #2529
Changelog category (leave one):
CI/CD Options
Exclude tests:
Regression jobs to run: