Initial sanitizer configurations by RSingh1511 · Pull Request #1 · eclipse-score/score_cpp_policies

RSingh1511 · 2026-03-03T15:00:12Z

Summary

Adds centralized sanitizer configurations (ASan, TSan, UBSan, LSan) for S-CORE C++ projects as a reusable Bazel module.

What's Included

Sanitizer configs with CI-optimized runtime options
Test workspace with positive and negative tests
CI workflow with GitHub Actions
PR/issue templates

Usage

bazel_dep(name = "score_cpp_policies", version = "0.0.0")

Signed-off-by: rahul.singh <rahul.sa.singh@partner.bmwgroup.com>

stmuench · 2026-03-04T07:22:15Z

.github/workflows/tests.yml

+jobs:
+  test-sanitizers:
+    name: Validate sanitizer configs
+    runs-on: ubuntu-latest


why using latest? this can easily break our workflows in case it gets upgraded

Fixed to ubuntu-24.04 for stability

stmuench · 2026-03-04T07:27:58Z

tests/sample_test.cpp

+    EXPECT_EQ(counter.load(), 4000);
+}
+
+// Test for undefined behavior detection (UBSan)


this comment is highly misleading. the below test does not contain any UB hence, how shall it help for verifying UB detection? better adjust the comment

stmuench · 2026-03-04T07:28:27Z

tests/sample_test.cpp

+    EXPECT_EQ(vec[4], 5);
+}
+
+// Test that allocates memory (for ASan/LSan validation)


how about

Suggested change

// Test that allocates memory (for ASan/LSan validation)

// Memory allocation test that should pass with all sanitizers

?

stmuench · 2026-03-04T07:31:04Z

tests/MODULE.bazel

+bazel_dep(name = "score_bazel_cpp_toolchains", version = "0.2.2")
+bazel_dep(name = "score_bazel_platforms", version = "0.0.4")


Why are these two required here? Where are they used actually?

stmuench · 2026-03-04T07:32:13Z

README.md

+- `--config=asan` - AddressSanitizer (memory errors, buffer overflows)
+- `--config=tsan` - ThreadSanitizer (data races, deadlocks)
+- `--config=ubsan` - UndefinedBehaviorSanitizer (undefined behavior)
+- `--config=lsan` - LeakSanitizer (memory leaks)


prefer alphabetical sorting instead?

Suggested change

- `--config=asan` - AddressSanitizer (memory errors, buffer overflows)

- `--config=tsan` - ThreadSanitizer (data races, deadlocks)

- `--config=ubsan` - UndefinedBehaviorSanitizer (undefined behavior)

- `--config=lsan` - LeakSanitizer (memory leaks)

- `--config=asan` - AddressSanitizer (memory errors, buffer overflows)

- `--config=lsan` - LeakSanitizer (memory leaks)

- `--config=tsan` - ThreadSanitizer (data races, deadlocks)

- `--config=ubsan` - UndefinedBehaviorSanitizer (undefined behavior)

stmuench · 2026-03-04T07:33:25Z

sanitizer/sanitizer.bazelrc

how about preferring plural here? would be more appropriate in my eyes since it makes clear that it will contain multiple sanitizer configs

i.e. sanitizers/sanitizers.bazelrc

stmuench · 2026-03-04T07:39:06Z

sanitizer/sanitizer.bazelrc

+# *******************************************************************************
+
+# ASan + UBSan + LSan (Combined - recommended for most testing)
+test:asan_ubsan_lsan --compilation_mode=dbg


please do not use dbg compliation mode. this would potentially enable code which is not part of the actual production code and hence you would potentially run into different code paths. just omit that everywhere since such compilation flags must come from the toolchain which defines the respective sanitizer features.
also see https://github.com/eclipse-score/communication/blob/main/quality/sanitizer/sanitizer.bazelrc#L20-L30 for further reference which flags we require for sanitizer configs

Removed compilation_mode=dbg and Done as suggested.

stmuench · 2026-03-04T07:40:16Z

sanitizer/sanitizer.bazelrc

+test:tsan --compilation_mode=dbg
+test:tsan --features=tsan
+test:tsan --platform_suffix=tsan


here and also for all the other configs:

Suggested change

test:tsan --compilation_mode=dbg

test:tsan --features=tsan

test:tsan --platform_suffix=tsan

build:tsan --features=tsan

build:tsan --platform_suffix=tsan

only the runtime options should get added as test config, the others are build configs!

stmuench · 2026-03-04T07:42:48Z

sanitizer/sanitizer.bazelrc

+test:asan_ubsan_lsan --test_env=ASAN_OPTIONS=exitcode=55:allow_addr2line=1:verbosity=1:detect_leaks=1:halt_on_error=1:allocator_may_return_null=1
+test:asan_ubsan_lsan --test_env=UBSAN_OPTIONS=exitcode=55:allow_addr2line=1:verbosity=1:print_stacktrace=1:halt_on_error=1
+test:asan_ubsan_lsan --test_env=LSAN_OPTIONS=exitcode=55:allow_addr2line=1:verbosity=1:halt_on_error=1


such runtime options should get extracted into a single place and then reused here instead

Suggested change

test:asan_ubsan_lsan --test_env=ASAN_OPTIONS=exitcode=55:allow_addr2line=1:verbosity=1:detect_leaks=1:halt_on_error=1:allocator_may_return_null=1

test:asan_ubsan_lsan --test_env=UBSAN_OPTIONS=exitcode=55:allow_addr2line=1:verbosity=1:print_stacktrace=1:halt_on_error=1

test:asan_ubsan_lsan --test_env=LSAN_OPTIONS=exitcode=55:allow_addr2line=1:verbosity=1:halt_on_error=1

test:_asan_runtime_options --test_env=ASAN_OPTIONS=exitcode=55:allow_addr2line=1:verbosity=1:detect_leaks=1:halt_on_error=1:allocator_may_return_null=1

test:_asan_runtime_options --test_env=LSAN_OPTIONS=exitcode=55:allow_addr2line=1:verbosity=1:halt_on_error=1

test:_ubsan_runtime_options --test_env=UBSAN_OPTIONS=exitcode=55:allow_addr2line=1:verbosity=1:print_stacktrace=1:halt_on_error=1

<...>

test:asan_ubsan_lsan --config=_asan_runtime_options

test:asan_ubsan_lsan --config=_lsan_runtime_options

test:asan_ubsan_lsan --config=_ubsan_runtime_options

<...>

test:asan --config=_asan_runtime_options

and please use the following runtime options instead:

test:_asan_runtime_options --test_env=ASAN_OPTIONS="exitcode=55 allow_addr2line=1 halt_on_error=1 print_stats=1 verbosity=1 allocator_may_return_null=1 check_initialization_order=1 detect_leaks=1 detect_stack_use_after_return=1 strict_string_checks=1"

test:_lsan_runtime_options --test_env=LSAN_OPTIONS="exitcode=55 allow_addr2line=1 halt_on_error=1 print_stats=1 verbosity=1"

test:_ubsan_runtime_options --test_env=UBSAN_OPTIONS="exitcode=55 allow_addr2line=1 halt_on_error=1 print_stacktrace=1 verbosity=1"

test:_tsan_runtime_options --test_env=TSAN_OPTIONS="exitcode=55 allow_addr2line=1 halt_on_error=1 print_stats=1 verbosity=1 detect_deadlocks=1 second_deadlock_stack=1"

Done as suggested.

stmuench · 2026-03-04T08:07:47Z

.github/workflows/tests.yml

+      - name: Test with ${{ matrix.config }}
+        working-directory: tests
+        run: |
+          bazel test --config=${{ matrix.config }} //:sample_test --verbose_failures


why not

Suggested change

bazel test --config=${{ matrix.config }} //:sample_test --verbose_failures

bazel test --config=${{ matrix.config }} //... --verbose_failures

?
since there will be further unit tests in this repo soon

Done as suggested.

4og · 2026-03-04T08:15:27Z

MODULE.bazel

+
+module(
+    name = "score_cpp_policies",
+    version = "0.0.1",


Can you please set the version to 0.0.0 here? The workflow in the S-CORE bazel registry is taking care of generating a patch when a release is picked.

Done as suggested.

4og · 2026-03-04T08:20:27Z

LICENSE.md

@@ -0,0 +1,13 @@
+Copyright 2026 Contributors to the Eclipse Foundation


Please put the entire license text here and remove .md extension. You can copy it,for example for here: https://github.com/eclipse-score/module_template/blob/main/LICENSE

General guideline: https://www.eclipse.org/projects/handbook/#legaldoc-license

4og · 2026-03-04T08:22:52Z

CONTRIBUTION.md

+
+The [Eclipse Safe Open Vehicle Core (S-CORE)](https://projects.eclipse.org/projects/automotive.score) project develops an open-source core stack for Software Defined Vehicles (SDVs). This repository centralizes the shared C++ quality tool policies (sanitizers, clang-tidy, clang-format) that S-CORE modules reuse to maintain consistent, safety-focused defaults.
+
+Project communication happens via the [score-dev mailing list](https://accounts.eclipse.org/mailing-list/score-dev), GitHub issues and pull requests, and the [Eclipse SCORE chatroom](https://chat.eclipse.org/#/room/#automotive.score:matrix.eclipse.org).


Where is the statement coming from? S-CORE is not using Eclipse matrix chat for communication, but Slack instead.

Removed Matrix chat reference, S-CORE uses Slack

FScholPer

Add the template please

RSingh1511 · 2026-03-05T08:26:11Z

Add the template please

Done>

4og · 2026-03-05T11:26:11Z

.github/workflows/tests.yml

+# *******************************************************************************
+
+name: Tests
+


Please limit permissions for security

Suggested change

permissions:

contents: read

4og · 2026-03-05T11:27:44Z

tests/sample_test.cpp

@@ -0,0 +1,62 @@
+// *******************************************************************************


Should we also have a second test that fails in sanitizers? Otherwise, how can we know that they work?

4og · 2026-03-05T11:34:42Z

.github/workflows/tests.yml

+          disk-cache: ${{ github.workflow }}-${{ matrix.config }}
+          cache-save: ${{ github.event_name == 'push' }}


For this kind of small implementation, caching in github is superfluous IMHO. It will make the build just longer. I wouldn't introduce it yet.
But how about adding bazelisk? This one can actually help (you'll also need to add .bazelversion file(s).

Suggested change

disk-cache: ${{ github.workflow }}-${{ matrix.config }}

cache-save: ${{ github.event_name == 'push' }}

bazelisk-cache: true

cache-save: ${{ github.event_name == 'push' }}

4og · 2026-03-05T11:35:01Z

.github/workflows/tests.yml

+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4


Suggested change

uses: actions/checkout@v4

uses: actions/checkout@v6

4og · 2026-03-05T11:35:42Z

.github/workflows/tests.yml

+
+      - name: Upload test logs on failure
+        if: failure()
+        uses: actions/upload-artifact@v4


Suggested change

uses: actions/upload-artifact@v4

uses: actions/upload-artifact@v7

stmuench · 2026-03-06T06:54:12Z

sanitizers/sanitizers.bazelrc

+# *******************************************************************************
+
+# ==============================================================================
+# Centralized Google Sanitizer Configurations for S-CORE C++ Modules


let's omit the term Google here, what do you think?

stmuench · 2026-03-06T06:55:56Z

README.md

-# Import centralized sanitizer configurations
-try-import %workspace%/../../../external/score_cpp_policies/sanitizer/sanitizer.bazelrc
+# Import centralized sanitizer configurations (fails if not found)
+import %workspace%/external/score_cpp_policies~/sanitizers/sanitizers.bazelrc


~ in between directory names intended here?

Changed to copy pattern instead of import.

stmuench · 2026-03-06T06:57:02Z

.github/ISSUE_TEMPLATE/bug_report.md

+
+### Observed behavior:
+
+### Expected behavior


### Expected behavior:

stmuench · 2026-03-06T06:58:38Z

.github/pull_request_template.md

+
+## Checklist for the PR Reviewer
+
+* [ ] Commits are properly organized and messages are according to the guideline


could we link such guidelines here as a direct reference for people?

stmuench · 2026-03-06T07:01:07Z

tests/BUILD.bazel

+cc_binary(
+    name = "asan_fail",
+    srcs = ["negative/asan_fail.cpp"],
+    tags = ["manual"],
+    testonly = True,
+)
+
+cc_binary(
+    name = "lsan_fail",
+    srcs = ["negative/lsan_fail.cpp"],
+    tags = ["manual"],
+    testonly = True,
+)
+
+cc_binary(
+    name = "tsan_fail",
+    srcs = ["negative/tsan_fail.cpp"],
+    tags = ["manual"],
+    testonly = True,
+)
+
+cc_binary(
+    name = "ubsan_fail",
+    srcs = ["negative/ubsan_fail.cpp"],
+    tags = ["manual"],
+    testonly = True,
+)


you should wrap an sh script around the invocation of each test instead and then add them as sh_test here. Within the sh script, you would have to verify that the test executable fails with exitcode 55.
Do you get my my idea?
Since then, you can remove the manual tags and have these tests running in CI as well ;)

Thanks for your suggestion. Done.

stmuench · 2026-03-06T07:57:57Z

sanitizers/BUILD.bazel

+# *******************************************************************************
+
+exports_files(
+    ["sanitizer.bazelrc"],


Suggested change

["sanitizer.bazelrc"],

["sanitizers.bazelrc"],

stmuench · 2026-03-06T08:00:24Z

tests/.bazelversion

@@ -0,0 +1 @@
+8.3.0


why is this required here?

do we really want to have the tests as separate module?

why is this required here?

Added per @4og 's feedback to enable bazelisk caching

do we really want to have the tests as separate module?

Yes, this follows the standard SCORE pattern used in score_rust_policies and other policy repos.

stmuench · 2026-03-06T08:00:47Z

tests/BUILD.bazel

+# *******************************************************************************
+# Copyright (c) 2026 Contributors to the Eclipse Foundation
+#
+# SPDX-License-Identifier: Apache-2.0
+# *******************************************************************************


why is this license statement different from others?

stmuench · 2026-03-06T08:03:26Z

tests/BUILD.bazel

+# ==============================================================================
+
+cc_binary(
+    name = "asan_fail_bin",


why not

Suggested change

name = "asan_fail_bin",

name = "asan_fail_test",

since _bin might be misleading

stmuench · 2026-03-06T11:38:24Z

README.md

 ```

-Add to your module's `.bazelrc`:
+Copy these configurations to your project's `.bazelrc`:


NO, I have to object here. we need to find a mechsnism to make this work centrally, e.g. via run_under and using a centralized script then. otherwise the settings we define here will simply get duplicated everywhere and these will deviate over time then which is not maintainable at all!

Agree. The whole point of this repository is to avoid duplication of sanitizer config, and now the README is just asking to duplicate 🤦‍♂️

Added --run_under as suggested.

… repo

stmuench · 2026-03-11T13:18:20Z

sanitizers/templates/asan_ubsan_lsan.env.template

+ASAN_OPTIONS=exitcode=55 allow_addr2line=1 verbosity=1 coverage=1 check_initialization_order=1 detect_stack_use_after_return=1 print_stats=1 halt_on_error=1 allocator_may_return_null=1 detect_leaks=1 suppressions=%ROOT%sanitizers/suppressions/asan.supp
+UBSAN_OPTIONS=exitcode=55 allow_addr2line=1 verbosity=1 coverage=1 print_stacktrace=1 halt_on_error=1 suppressions=%ROOT%sanitizers/suppressions/ubsan.supp
+LSAN_OPTIONS=exitcode=55 suppressions=%ROOT%sanitizers/suppressions/lsan.supp


why do we need the coverage=1 flag?

You're right - the coverage=1 flag was copied from communication's sanitizer config, but it's not necessary.

stmuench · 2026-03-11T13:18:49Z

sanitizers/templates/tsan.env.template

@@ -0,0 +1 @@
+TSAN_OPTIONS=exitcode=55 allow_addr2line=1 verbosity=1 coverage=1 detect_deadlocks=1 second_deadlock_stack=1 halt_on_error=0 suppressions=%ROOT%sanitizers/suppressions/tsan.supp


why not

Suggested change

TSAN_OPTIONS=exitcode=55 allow_addr2line=1 verbosity=1 coverage=1 detect_deadlocks=1 second_deadlock_stack=1 halt_on_error=0 suppressions=%ROOT%sanitizers/suppressions/tsan.supp

TSAN_OPTIONS=exitcode=55 allow_addr2line=1 verbosity=1 detect_deadlocks=1 second_deadlock_stack=1 halt_on_error=1 suppressions=%ROOT%sanitizers/suppressions/tsan.supp

?

stmuench · 2026-03-11T13:20:05Z

sanitizers/sanitizers.bazelrc

+test:asan_ubsan_lsan --run_under=@score_cpp_policies//sanitizers:wrapper
+
+# AddressSanitizer only
+test:asan  --config=asan_ubsan_lsan


Suggested change

test:asan --config=asan_ubsan_lsan

build:asan --config=asan_ubsan_lsan

stmuench · 2026-03-11T13:20:17Z

sanitizers/sanitizers.bazelrc

+test:asan  --test_tag_filters=-no-asan
+
+# UndefinedBehaviorSanitizer only
+test:ubsan --config=asan_ubsan_lsan


Suggested change

test:ubsan --config=asan_ubsan_lsan

build:ubsan --config=asan_ubsan_lsan

stmuench · 2026-03-11T13:20:28Z

sanitizers/sanitizers.bazelrc

+test:ubsan --test_tag_filters=-no-ubsan
+
+# LeakSanitizer only
+test:lsan  --config=asan_ubsan_lsan


Suggested change

test:lsan --config=asan_ubsan_lsan

build:lsan --config=asan_ubsan_lsan

4og · 2026-03-11T16:15:15Z

README.md

+### Step 1 — Add to `MODULE.bazel`
+
+```python
+bazel_dep(name = "score_cpp_policies", version = "0.0.0")
+
+# For local development (repos checked out side-by-side):
+local_path_override(
+    module_name = "score_cpp_policies",
+    path = "../score_cpp_policies",
+)
+```
+
+### Step 2 — Import in `.bazelrc`
+
+```bazelrc
+try-import %workspace%/../score_cpp_policies/sanitizers/sanitizers.bazelrc
+```
+
+> `try-import` silently skips if the path does not exist (e.g. in CI). For published modules consumed via bzlmod, copy the contents of `sanitizers/sanitizers.bazelrc` directly into your `.bazelrc` instead.
+


This part is not very useful unfortunately. The score_cpp_policies is going to be pushed to bazel registry and consumed by other modules as a regular (dev-)dependency. I doubt anyone is going to locally cloning this repo and modifying their .bazelrc

Updated README.

4og · 2026-03-11T16:16:46Z

README.md

+| `sanitizers/suppressions/tsan.supp` | TSan | *(empty)* |
+| `sanitizers/suppressions/ubsan.supp` | UBSan | *(empty)* |
+
+To add suppressions for libraries used across S-CORE modules, open a PR against this repository.


I believe suppressions should live in the module repos if they suppress code in those repos. How can it be done?

suppressions specific to one module should live in that module's repo.

4og · 2026-03-11T16:19:12Z

README.md

+| Option | Value | Purpose |
+|--------|-------|---------|
+| `exitcode` | `55` | Custom exit code to distinguish sanitizer failures from test failures in CI |
+| `halt_on_error` | `1` | Stop on first error for faster feedback |
+| `verbosity` | `1` | Detailed error reports with stack traces |
+| `allow_addr2line` | `1` | Enable symbolization for readable stack traces |
+| `coverage` | `1` | Track code coverage information |
+| `print_stats` | `1` | Print allocator statistics on exit |
+| `allocator_may_return_null` | `1` | Allocator returns null instead of crashing on OOM |
+| `detect_leaks` | `1` | Enable leak detection (LSan) |
+| `check_initialization_order` | `1` | Detect globals accessed before initialization |
+| `detect_stack_use_after_return` | `1` | Detect stack use-after-return bugs |
+| `print_stacktrace` (UBSan) | `1` | Print stack trace for each UBSan finding |
+| `suppressions` | `<path>/*.supp` | Suppression files (absolute paths, resolved by wrapper) |
+
+### ThreadSanitizer
+
+| Option | Value | Purpose |
+|--------|-------|---------|
+| `exitcode` | `55` | Same custom exit code |
+| `halt_on_error` | `0` | TSan continues after errors (reports all data races) |
+| `verbosity` | `1` | Detailed error reports |
+| `allow_addr2line` | `1` | Enable symbolization |
+| `coverage` | `1` | Track coverage |
+| `detect_deadlocks` | `1` | Detect potential deadlocks |
+| `second_deadlock_stack` | `1` | Show both stacks involved in deadlocks |
+| `suppressions` | `<path>/tsan.supp` | Suppression file (absolute path) |


Is it possible to add these explanations directly to the .template files as a comment? Otherwise, it will quickly go unsync

4og · 2026-03-11T16:21:26Z

README.md

+This design ensures:
+- Suppression files are always found, even when consuming `score_cpp_policies` as an external bzlmod dependency
+- Runtime options are updated by bumping the module version (no consumer changes needed)
+- All sanitizer logic is centralized — consumers only configure **which** sanitizers to enable


I don't find these implementation details useful in the main readme file. The wrapper script is effectively just 5 lines of code.

4og · 2026-03-11T16:23:16Z

sanitizers/sanitizers.bazelrc

@@ -0,0 +1,59 @@
+# *******************************************************************************


I still have troubles to understand how users of the score_cpp_policies module are going to consume this file.

-> eclipse-score/communication#182

Initial sanitizer configurations

03330fd

Signed-off-by: rahul.singh <rahul.sa.singh@partner.bmwgroup.com>

RSingh1511 marked this pull request as draft March 3, 2026 15:00

Add tests and CI workflow

0074202

Signed-off-by: rahul.singh <rahul.sa.singh@partner.bmwgroup.com>

RSingh1511 requested review from 4og, antonkri, pawelrutkaq and rmaddikery March 4, 2026 04:02

RSingh1511 marked this pull request as ready for review March 4, 2026 04:07

RSingh1511 requested a review from FScholPer March 4, 2026 04:08

stmuench suggested changes Mar 4, 2026

View reviewed changes

4og requested changes Mar 4, 2026

View reviewed changes

Address all PR review feedback

e54b31b

RSingh1511 requested review from 4og and stmuench March 5, 2026 05:55

FScholPer requested changes Mar 5, 2026

View reviewed changes

Add PR and issue templates

b5133ac

RSingh1511 requested a review from FScholPer March 5, 2026 08:26

4og requested changes Mar 5, 2026

View reviewed changes

Address workflow review comments

704598f

RSingh1511 requested a review from 4og March 5, 2026 12:28

Add manual negative tests to verify sanitizers work

6f1128b

stmuench suggested changes Mar 6, 2026

View reviewed changes

Convert negative tests to automated sh_test with exit code validation

f32f51e

RSingh1511 requested a review from stmuench March 6, 2026 07:50

stmuench reviewed Mar 6, 2026

View reviewed changes

Fix BUILD.bazel issues per review feedback

6ad8f42

RSingh1511 requested a review from stmuench March 6, 2026 08:24

Address review comments: fix templates, change to copy pattern

5f0d254

stmuench suggested changes Mar 6, 2026

View reviewed changes

RSingh1511 force-pushed the rs/swp-245137 branch from 11d6970 to 36517ef Compare March 10, 2026 15:50

FScholPer previously approved these changes Mar 10, 2026

View reviewed changes

RSingh1511 dismissed FScholPer’s stale review via 6ca1910 March 11, 2026 05:18

RSingh1511 force-pushed the rs/swp-245137 branch from 36517ef to 6ca1910 Compare March 11, 2026 05:18

RSingh1511 requested a review from FScholPer March 11, 2026 05:20

RSingh1511 force-pushed the rs/swp-245137 branch 3 times, most recently from 5aeeea5 to c504ee0 Compare March 11, 2026 12:29

Add centralized sanitizer infrastructure extracted from communication…

cf027ca

… repo

RSingh1511 force-pushed the rs/swp-245137 branch from c504ee0 to cf027ca Compare March 11, 2026 12:46

stmuench reviewed Mar 11, 2026

View reviewed changes

Remove coverage flag and fix TSan halt_on_error per review

309e43d

RSingh1511 requested a review from stmuench March 11, 2026 13:53

4og requested changes Mar 11, 2026

View reviewed changes

RSingh1511 force-pushed the rs/swp-245137 branch 6 times, most recently from 789a32e to 0413906 Compare March 12, 2026 08:39

Address review feedback: simplify docs and fix tag filters

d6f8104

RSingh1511 force-pushed the rs/swp-245137 branch from 0413906 to d6f8104 Compare March 12, 2026 08:58

Improve sanitizer configuration documentation

7d2f594

RSingh1511 requested a review from 4og March 12, 2026 14:16

Generalize TSan suppressions for Rust test runner

07a78d6

RSingh1511 force-pushed the rs/swp-245137 branch from 1566f5a to 07a78d6 Compare March 16, 2026 06:29

	// Test that allocates memory (for ASan/LSan validation)
	// Memory allocation test that should pass with all sanitizers

		bazel_dep(name = "score_bazel_cpp_toolchains", version = "0.2.2")
		bazel_dep(name = "score_bazel_platforms", version = "0.0.4")

-test:asan_ubsan_lsan --test_env=ASAN_OPTIONS=exitcode=55:allow_addr2line=1:verbosity=1:detect_leaks=1:halt_on_error=1:allocator_may_return_null=1
-test:asan_ubsan_lsan --test_env=UBSAN_OPTIONS=exitcode=55:allow_addr2line=1:verbosity=1:print_stacktrace=1:halt_on_error=1
-test:asan_ubsan_lsan --test_env=LSAN_OPTIONS=exitcode=55:allow_addr2line=1:verbosity=1:halt_on_error=1
+test:_asan_runtime_options --test_env=ASAN_OPTIONS=exitcode=55:allow_addr2line=1:verbosity=1:detect_leaks=1:halt_on_error=1:allocator_may_return_null=1
+test:_asan_runtime_options --test_env=LSAN_OPTIONS=exitcode=55:allow_addr2line=1:verbosity=1:halt_on_error=1
+test:_ubsan_runtime_options --test_env=UBSAN_OPTIONS=exitcode=55:allow_addr2line=1:verbosity=1:print_stacktrace=1:halt_on_error=1
+<...>
+test:asan_ubsan_lsan --config=_asan_runtime_options
+test:asan_ubsan_lsan --config=_lsan_runtime_options
+test:asan_ubsan_lsan --config=_ubsan_runtime_options
+<...>
+test:asan --config=_asan_runtime_options

	bazel test --config=${{ matrix.config }} //:sample_test --verbose_failures
	bazel test --config=${{ matrix.config }} //... --verbose_failures

		@@ -0,0 +1,13 @@
		Copyright 2026 Contributors to the Eclipse Foundation


		The [Eclipse Safe Open Vehicle Core (S-CORE)](https://projects.eclipse.org/projects/automotive.score) project develops an open-source core stack for Software Defined Vehicles (SDVs). This repository centralizes the shared C++ quality tool policies (sanitizers, clang-tidy, clang-format) that S-CORE modules reuse to maintain consistent, safety-focused defaults.

		Project communication happens via the [score-dev mailing list](https://accounts.eclipse.org/mailing-list/score-dev), GitHub issues and pull requests, and the [Eclipse SCORE chatroom](https://chat.eclipse.org/#/room/#automotive.score:matrix.eclipse.org).

		# *******************************************************************************

		name: Tests

		@@ -0,0 +1,62 @@
		// *******************************************************************************

		disk-cache: ${{ github.workflow }}-${{ matrix.config }}
		cache-save: ${{ github.event_name == 'push' }}

	uses: actions/upload-artifact@v4
	uses: actions/upload-artifact@v7

		@@ -0,0 +1 @@
		8.3.0


		## Checklist for the PR Reviewer

		* [ ] Commits are properly organized and messages are according to the guideline

		@@ -0,0 +1 @@
		TSAN_OPTIONS=exitcode=55 allow_addr2line=1 verbosity=1 coverage=1 detect_deadlocks=1 second_deadlock_stack=1 halt_on_error=0 suppressions=%ROOT%sanitizers/suppressions/tsan.supp

	test:asan --config=asan_ubsan_lsan
	build:asan --config=asan_ubsan_lsan

	test:ubsan --config=asan_ubsan_lsan
	build:ubsan --config=asan_ubsan_lsan

	test:lsan --config=asan_ubsan_lsan
	build:lsan --config=asan_ubsan_lsan

		@@ -0,0 +1,59 @@
		# *******************************************************************************

Conversation

RSingh1511 commented Mar 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

What's Included

Usage

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

RSingh1511 Mar 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

4og Mar 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

FScholPer left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

RSingh1511 commented Mar 5, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

RSingh1511 commented Mar 3, 2026 •

edited

Loading

RSingh1511 Mar 5, 2026 •

edited

Loading

4og Mar 4, 2026 •

edited

Loading

FScholPer left a comment •

edited

Loading