Repository navigation
Conversation
arkjedrz
commented
Oct 23, 2026
Contributor
- Add score.bazelrc/score_sanitizers.bazelrc from baselibs (asan, ubsan, lsan, tsan, asan_ubsan_lsan, tsan_ubsan) and import it from .bazelrc in baselibs' order. The features come from the @score_cpp_policies toolchain injection in MODULE.bazel.
- Add sanitizers_linux.yml, modeled on baselibs. It runs bazel test --config=score-linux-x86_64 --config=asan_ubsan_lsan on //score/... with the cicd common steps and SHA pins, and uploads the test logs. It can be called with workflow_call.
Contributor
License Check Results🚀 The license check job ran with the Bazel command: bazel run --lockfile_mode=error //:license-checkStatus: Click to expand output |
Contributor
|
Documentation preview for this pull request is available at: |
- Move the Ruff config from pyproject.toml to ruff.toml. - Add the baselibs lint wiring: .clang-tidy, tools/lint/linters.bzl and score.bazelrc/score_lint.bazelrc, imported from .bazelrc. build:lint adds --config=score-linux-x86_64 first, because cicd static-analysis.yml passes only --config=lint. - Run Clippy through the rules_rust clippy aspect with the score_rust_policies strict clippy.toml. aspect_rules_lint stays at 2.7.2, which no longer has the lint/clippy.bzl that the score_rust_policies 0.0.5 aspect loads. - Promote the 85 carved-out clang-tidy checks without findings to errors. - Rename clippy.yml to lint.yml. It lints //... with bazel-config lint and can be called with workflow_call. - Replace the README Clippy section with a Lint section. - Clarify the HeaderFilterRegex comment in .clang-tidy. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
- Pin aspect_rules_lint 2.5.2. 2.6.0 removed lint/clippy.bzl, which @score_rust_policies//clippy:linters.bzl still loads. - Use baselibs' build:clippy lines (clippy_strict aspect, rules_lint_human, fail_on_violation) instead of rules_rust's rust_clippy_aspect. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
- Use ruff_lint_aspect from @score_tooling//third_party/lint instead of a local lint_ruff_aspect. - Keep the Ruff rules in pyproject.toml, as on main. Drop ruff.toml. ruff format and the Ruff aspect read the same file. - Export only .clang-tidy from the root BUILD for //tools/lint. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
- Move quality/coverage to tools/coverage, as in baselibs. Rewrite the //quality/coverage labels, the .bazelrc import, the comments in MODULE.bazel and BUILD, and the justifications path in coverage.yml and release.yml. - Align the llvm_cov config with baselibs. Set the platform and the LLVM and Ferrocene toolchains explicitly. Keep the warning feature disables and --instrumentation_filter=^//score[/:]. - Add baselibs' check_coverage_scope.sh and scope_exclusions.txt. The check fails when a production library under //score/... is neither in //tools/coverage:coverage_scope nor excluded. - Replace coverage.yml with coverage_report.yml. Use baselibs' triggers (push, merge_group, workflow_call) and steps, including the scope check, on the cicd common steps with SHA pins. Keep workflow_dispatch and the <repo>_coverage_report artifact name. - Drop the cargo-coverage job from check.yml. coverage_report.yml covers rust_kvs. cpp-bazel stays until check.yml is replaced. - Document the scope check and coverage_report.yml in tools/coverage/README.md. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
- Add score.bazelrc/score_sanitizers.bazelrc from baselibs (asan, ubsan, lsan, tsan, asan_ubsan_lsan, tsan_ubsan) and import it from .bazelrc in baselibs' order. The features come from the @score_cpp_policies toolchain injection in MODULE.bazel. - Add sanitizers_linux.yml, modeled on baselibs. It runs bazel test --config=score-linux-x86_64 --config=asan_ubsan_lsan on //score/... with the cicd common steps and SHA pins, and uploads the test logs. It can be called with workflow_call. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
arkjedrz
force-pushed
the
arkjedrz_tooling-07-sanitizers
branch
from
October 26, 2026 14:58
dfc203a to
ff1742b
Compare
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.