[all-commits] [llvm/llvm-project] 63cb4e: [libc++] Use a self-contained job to run libstdc++...

[Louis Dionne via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 63cb4e37ce2caf24426c08cf54c11e44f80d1fb0
      https://github.com/llvm/llvm-project/commit/63cb4e37ce2caf24426c08cf54c11e44f80d1fb0
  Author: Louis Dionne <ldionne.2 at gmail.com>
  Date:   2026-09-28 (Mon, 28 Sep 2026)

  Changed paths:
    M .github/workflows/libcxx-benchmark-commit.yml
    A .github/workflows/libcxx-benchmark-libstdcxx.yml
    M libcxx/utils/ci/lnt/README.md
    M libcxx/utils/ci/lnt/machines.json
    A libcxx/utils/ci/lnt/run-libstdcxx-benchmarks
    R libcxx/utils/ci/lnt/schema.yaml
    A libcxx/utils/ci/lnt/schemas/libcxx.yaml
    A libcxx/utils/ci/lnt/schemas/libstdcxx.yaml

  Log Message:
  -----------
  [libc++] Use a self-contained job to run libstdc++ benchmarks (#226985)

After trying to retrofit libstdc++ benchmarking into our existing libc++
pipeline, I am giving up and setting up a self-contained job to do it
instead. It's much simpler as we can just run exactly what we need
instead of fighting to decouple libc++ specific logic from the libc++
benchmarking pipeline.

Various parts can still be extracted (e.g. gathering hardware
information for LNT reports, reading machines.json, etc) and will be
extracted in future iterations.

Also, add the corresponding libstdcxx LNT test suite schema so we can
start submitting results to it.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications