Skip to content

Force Clang for branch B in Benchmark Compare workflow - #67

Closed
lubyant wants to merge 2 commits into
mainfrom
ci/benchmark-compiler-compare
Closed

lubyant wants to merge 2 commits into
mainfrom
ci/benchmark-compiler-compare

Conversation

@lubyant

@lubyant lubyant commented Aug 1, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • Reuses the existing Benchmark Compare (branch-vs-branch) workflow instead of adding a new one.
  • Branch B's build step now explicitly sets CC=clang CXX=clang++ (non-Windows), while branch A keeps the runner's default compiler (gcc on Linux). Dispatching with branch_a=main, branch_b=<this branch> therefore profiles GCC vs Clang on identical source rather than a source diff.
  • Windows branch B is left untouched (MSVC-only, no native gcc/clang pair to compare).

Test plan

  • Trigger Benchmark Compare via workflow_dispatch with branch_a=main, branch_b=ci/benchmark-compiler-compare and confirm the summary shows a GCC vs Clang diff.

The existing Benchmark Compare workflow diffs two branches/refs but always
builds each with whatever compiler the runner defaults to, so it can't
isolate compiler choice. This adds a workflow_dispatch job that builds a
single ref with both GCC and Clang (separate build trees so neither shares
generated dependency build files) and diffs the results with
benchmark's compare.py.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@codecov

codecov Bot commented Aug 1, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.48%. Comparing base (6a0241c) to head (e0e5bf8).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #67   +/-   ##
=======================================
  Coverage   93.48%   93.48%           
=======================================
  Files          16       16           
  Lines         937      937           
  Branches      416      416           
=======================================
  Hits          876      876           
  Misses         12       12           
  Partials       49       49           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Drop the separate new workflow in favor of reusing the existing branch-vs-branch
Benchmark Compare workflow: branch B now explicitly builds with clang/clang++
(branch A keeps the runner default, gcc on Linux), so dispatching with
branch_a=main, branch_b=<this branch> profiles compiler choice instead of a
source diff.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@lubyant lubyant changed the title Add GCC vs Clang benchmark comparison workflow Force Clang for branch B in Benchmark Compare workflow Aug 1, 2026
@lubyant lubyant closed this Aug 2, 2026
@lubyant
lubyant deleted the ci/benchmark-compiler-compare branch August 2, 2026 04:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant