chore(CI): add example check on asan test

[LHT129]

Summary by Sourcery

Add CI jobs to run ASan-instrumented example binaries on both x86 and AArch64 builds.

CI:

• Add ASan-based example test job for x86 artifacts in the asan_build_and_test workflow.
• Add ASan-based example test job for AArch64 artifacts in the asan_build_and_test workflow.

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[sourcery-ai]

Reviewer's Guide

Adds two new CI jobs to run ASan-instrumented example binaries for x86 and AArch64 artifacts in the GitHub Actions workflow.

File-Level Changes

Change	Details	Files
Add ASan example test job for x86 artifacts in CI.	Define new job that depends on the existing x86 ASan build job Run on ubuntu-22.04 runner and free disk space before execution Check out repository and clean any existing build directory Download x86 ASan test artifact into ./build using the GitHub run ID Iterate over all files in ./build/examples/cpp, make them executable, and run each binary	.github/workflows/asan_build_and_test.yml
Add ASan example test job for AArch64 artifacts in CI.	Define new job that depends on the existing AArch64 ASan build job Run on ubuntu-22.04-arm runner and free disk space before execution Check out repository and clean any existing build directory Download AArch64 ASan test artifact into ./build using the GitHub run ID Iterate over all files in ./build/examples/cpp, make them executable, and run each binary	.github/workflows/asan_build_and_test.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey there - I've reviewed your changes - here's some feedback:

• The for example in ./*; do loop will iterate over directories and non-binaries as well; consider restricting to regular files (e.g. via find . -maxdepth 1 -type f -executable) and quoting $example to avoid issues with spaces or non-executable entries.
• The test_example_x86 and test_example_aarch64 jobs are nearly identical; consider factoring the common steps into a matrix job or a reusable workflow to reduce duplication and keep the two architectures in sync more easily.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The `for example in ./*; do` loop will iterate over directories and non-binaries as well; consider restricting to regular files (e.g. via `find . -maxdepth 1 -type f -executable`) and quoting `$example` to avoid issues with spaces or non-executable entries.
- The `test_example_x86` and `test_example_aarch64` jobs are nearly identical; consider factoring the common steps into a matrix job or a reusable workflow to reduce duplication and keep the two architectures in sync more easily.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov]

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

❌ Your patch check has failed because the patch coverage (0.00%) is below the target coverage (80.00%). You can increase the patch coverage or adjust the target coverage.

@@            Coverage Diff             @@
##             main    #1381      +/-   ##
==========================================
- Coverage   91.13%   91.11%   -0.03%     
==========================================
  Files         327      327              
  Lines       19146    19147       +1     
==========================================
- Hits        17449    17446       -3     
- Misses       1697     1701       +4     

Flag	Coverage Δ
cpp	91.11% <0.00%> (-0.03%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
common	85.66% <ø> (ø)
datacell	93.52% <ø> (+0.90%)	⬆️
index	90.55% <0.00%> (-0.51%)	⬇️
simd	100.00% <ø> (ø)

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6fd27f6...34d1650. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[wxyucs]

lgtm