[CI] Add nightly ELD code coverage workflow with regression detection#1405
Open
Saharsh Burra (bsaharsh) wants to merge 1 commit into
Open
[CI] Add nightly ELD code coverage workflow with regression detection#1405Saharsh Burra (bsaharsh) wants to merge 1 commit into
Saharsh Burra (bsaharsh) wants to merge 1 commit into
Conversation
Saharsh Burra (bsaharsh)
force-pushed
the
add-coverage-regression-detection
branch
from
7ab5f2f to
5cb95b0
Compare
Shankar Easwaran (quic-seaswara)
requested changes
Jul 7, 2026
| git config user.name 'github-actions' | ||
| git config user.email 'github-actions@github.com' | ||
|
|
||
| git checkout --orphan coverage-update |
Contributor
There was a problem hiding this comment.
can we have this branch as code-coverage-reports ?
Contributor
Author
There was a problem hiding this comment.
Updated the name
Parth (parth-07)
requested review from
Steven Ramirez Rosa (Steven6798),
Parth (parth-07) and
quic-areg
| jobs: | ||
| coverage: | ||
| if: github.repository == 'qualcomm/eld' | ||
| runs-on: self-hosted |
Contributor
There was a problem hiding this comment.
Shankar Easwaran (@quic-seaswara) is it okay to run this workflow on self-hosted? self-hosted here will make adding this workflow easier because we would not need to install/setup the cross-toolchains and qemu.
| repository: ${{ github.repository }} | ||
| ref: ${{ github.ref_name }} | ||
| path: llvm-project/llvm/tools/eld | ||
| fetch-depth: 0 |
Contributor
There was a problem hiding this comment.
We can likely remove fetch-depth: 0 from here.
Contributor
Author
There was a problem hiding this comment.
Updated
| ../llvm-project/llvm \ | ||
| -DCMAKE_BUILD_TYPE=Debug \ | ||
| -DCMAKE_DISABLE_PRECOMPILE_HEADERS=ON \ | ||
| -DLLVM_ENABLE_PROJECTS="llvm;clang;clang-tools-extra" \ |
Contributor
There was a problem hiding this comment.
Would it be possible to use the clang and the other tools from the nightly eld toolchain and only build eld with code-coverage enabled?
Contributor
Author
There was a problem hiding this comment.
Updated, but need to test it as fork won't be having the self hosted, may be we can use the workflow dispatch.
Saharsh Burra (bsaharsh)
force-pushed
the
add-coverage-regression-detection
branch
from
5cb95b0 to
0149db3
Compare
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
Saharsh Burra (bsaharsh)
force-pushed
the
add-coverage-regression-detection
branch
2 times, most recently
from
531af9e to
60cec40
Compare
Parth (parth-07)
force-pushed
the
add-coverage-regression-detection
branch
3 times, most recently
from
aa5537f to
eb451ab
Compare
Saharsh Burra (bsaharsh)
force-pushed
the
add-coverage-regression-detection
branch
from
eb451ab to
10b8ddc
Compare
Parth (parth-07)
force-pushed
the
add-coverage-regression-detection
branch
from
49d7a22 to
4cd34c6
Compare
Saharsh Burra (bsaharsh)
force-pushed
the
add-coverage-regression-detection
branch
from
4cd34c6 to
8fcbdc7
Compare
Parth (parth-07)
force-pushed
the
add-coverage-regression-detection
branch
from
85f166b to
445434e
Compare
Add nightly-eld-code-coverage.yml which runs daily after the nightly build. The workflow: - Builds LLVM+ELD with source-based coverage instrumentation (ELD_COVERAGE=ON) - Runs the full check-eld test suite under LLVM_PROFILE_FILE to collect per-process .profraw files - Downloads LLVM 22.1.8 from GitHub Releases and uses its llvm-profdata and llvm-cov tools to avoid profraw version mismatches with the built-in tools - Merges profiles with llvm-profdata and generates an HTML report with llvm-cov show - Extracts Line/Function/Region/Branch percentages from the TOTAL row of llvm-cov report - Compares each metric against a coverage-baseline.txt stored on the code-coverage-reports branch; fails the workflow if any metric regresses - On first run (no baseline present) records the baseline without failing - Force-pushes the HTML report and updated baseline to the code-coverage-reports orphan branch on every successful run Also updates CMakeLists.txt: ELD_COVERAGE option now sets llvm-cov source-based instrumentation flags (-fprofile-instr-generate -fcoverage-mapping) instead of gcov (--coverage). Signed-off-by: bsaharsh <bsaharsh@qti.qualcomm.com>
Saharsh Burra (bsaharsh)
force-pushed
the
add-coverage-regression-detection
branch
from
445434e to
f7bb343
Compare
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
5 participants
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.
Added a workflow which runs nightly and computes the code coverage, and when ran at first creates a baseline text file on orphan branch called code-coverage, and from the next time, it checks with the previous coverage numbers and if any metric goes down, it fails, and if no regression is detected then we push the html report and update the baseline text file.