test/coverage: authoritative full-suite run 3 — 68.0% line / 50.2% branch - #95
Closed
gburd wants to merge 1 commit into
Closed
test/coverage: authoritative full-suite run 3 — 68.0% line / 50.2% branch#95gburd wants to merge 1 commit into
gburd wants to merge 1 commit into
Conversation
…nch) Fresh full-suite + all COV_* blocks on a dedicated c7i.24xlarge (96 vCPU, AL2023), master @ v5.3.32 (27f8e7b), gcc 11.5 -O0 --coverage, ONE build with .gcda accumulated across the parallel Tcl suite AND every COV_* block, merged in a single lcov capture from .libs. Headline (src/-only, dbinc_auto excluded, branch coverage on): line 68.0% (49192/72377) +20.0 vs authoritative 48.0, +5.7 vs interim 62.3 branch 50.2% (39238/78236) +14.1 vs authoritative 36.1, +4.0 vs interim 46.2 function 80.5% (2129/2644) Adds test/coverage/full_run3_combined.sh (the combined driver), FULL-COVERAGE-REPORT-3.md (report + honest path-to-80%), full-run-3/ (cov-src.info, ranking, subsystems, summary), and ratchets baseline.txt 62.3/46.2 -> 68.0/50.2. Caveats documented in the report: xa=0% in this capture (liburing-devel missing at build; XA driver re-ran PASS but instance was reclaimed before the re-capture was retrieved -> ~+0.3 pt pending); db_upgrade partial (synthetic hash-fixture bug); os_aio io_uring backend cold (ENOSYS on host). Measurement only -- no engine code touched.
Collaborator
Author
|
Superseded: the coverage report + baseline ratchet (68.0/50.2) were merged via #94, and the uniquely-valuable full_run3_combined.sh + cov-subsystems.txt are merged via #96. The remaining diff in this branch is stale duplicate content (db_join/db_method from #92, recd_handlers from #93, fi_sweep from #90 — all already on master). Thanks — the run itself produced the authoritative number. |
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
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.
Authoritative full-suite coverage run 3
Fresh, authoritative code-coverage measurement on a dedicated AWS EC2
c7i.24xlarge(96 vCPU, AL2023),master@ v5.3.32 (27f8e7b6c), then theinstance was terminated. Measurement/report only — no engine code changed.
ONE instrumented build (gcc 11.5,
-O0 -g --coverage),.gcdaaccumulatedacross the full parallel Tcl suite AND every COV_* block, merged in a
single
lcov --capture --directory .libs.Headline (src/-only,
dbinc_autoexcluded, branch coverage on)+20.0 pts line / +14.1 pts branch vs the authoritative baseline;
+5.7 / +4.0 vs the interim. Wall time ~89 min.
What ran
deadlock+DB_REGISTER drivers, and the C drivers (backup, os_aio, recd_compact PASS)
Honest caveats (see FULL-COVERAGE-REPORT-3.md)
liburing-develwas missing at build time, soxa_directfailed to link (-luring). After installing it the XA driverre-ran and PASSED, but the EC2 instance was reclaimed (went to
shutting-downon its own) before the re-capture could be pulled back — sothe verifiable headline is 68.0% with xa=0%; with XA counted it's ~68.3%.
Next round:
dnf install liburing-develup front.aborts on a spares-array bug (
run_upgrade.sh, not the engine).io_uring_queue_initreturned ENOSYS onthe host (kernel io_uring disabled). Other AIO backends covered.
Contents
test/coverage/full_run3_combined.sh— the combined drivertest/coverage/FULL-COVERAGE-REPORT-3.md— report + per-subsystem + top cold files + path-to-80%test/coverage/full-run-3/— cov-src.info, ranking, subsystems, summarytest/coverage/baseline.txt— ratcheted 62.3/46.2 → 68.0/50.2