Repository navigation
Conversation
ARM sanitizer builds disable SimSIMD so `02354_vector_search_rescoring_distance_in_select_list` disagrees with the binary-build reference. Co-authored-by: Cursor <[email protected]>
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 <[email protected]>
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 <[email protected]>
7 of 30 tasks
Most runners are in Hetzner, so every job that downloads the submodule archive from AWS S3 pays egress. Keep the archive in a Hetzner bucket instead. Buckets listed in `S3_EXTERNAL_BUCKETS` are served by a boto3 client with their own endpoint and credentials. `S3.put` and `S3.head_object` use it for those buckets, and keep using the AWS CLI for every other bucket. With `public_read`, reads are unsigned, so community PRs can use the archive without credentials; they never create it. A missing credential is an error, so ambient AWS credentials are never sent to the Hetzner endpoint. The archive is public, so `_prepare_submodule_cache` refuses to upload it if the clone token ended up in a git config file. The workflows export `HETZNER_S3_ACCESS_KEY` and `HETZNER_S3_SECRET_KEY` from GitHub secrets. The bucket is `altinity-builds-cache` in hel1. Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
The first CI run failed with a 403 on the existence check for the submodule archive. The bucket is public for object reads, but answers a HEAD of a missing key with 403 to callers who cannot list it. The config job read the bucket unsigned because the bucket is marked `public_read`, even though it has the keys. Reads are now unsigned only for jobs without the bucket's keys. Those jobs treat a 403 from `head_object` as a miss; jobs with the keys use a signed client, so a 403 is still an error for them. Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
`create_workflow_report.py` conflicted: `stable-26.8` refactored the release baseline lookup while this branch changed it to report the baseline commit time and to filter statuses by the reported ref. `antalya-26.8` already carries both, so take its version of the file. Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
This branch has not been deployed
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
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.
CICD Fixes and ports for 26.8
Changelog category (leave one):
CI/CD Options
Exclude tests:
Regression jobs to run: