mbarbin / fpath-base
100%

DEFAULT BRANCH: main
Repo Added
Token zgKxm2FP9ec4eHVBuERoSxj6NbDVehRhN regen
Build 132 Last
Files 22
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH main
branch: SELECT
CHANGE BRANCH
x
Sync Branches

coverage: 100.0% (+0.6%) from 99.364%
135

push

github

mbarbin 
Add test

9 of 9 new or added lines in 1 file covered. (100.0%)

953 of 953 relevant lines covered (100.0%)

9.86 hits per line

Relevant lines Covered
953 RELEVANT LINES 953 COVERED LINES
9.86 HITS PER LINE
Source Files on main

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
135 main Add test push mbarbin github
100.0
134 main Upgrade OCaml to latest available versions push mbarbin github
99.36
133 main Upgrade to latest mdexp push mbarbin github
99.36
132 main Upgrade OCaml and dune in CI push mbarbin github
99.36
131 main Fix some typos push mbarbin github
99.36
130 main Run the tests first and instrumented after that Pragmatically when running locally I have observed that this sequence usually ends up resolving the partial coverage report that otherwise gets generated sometimes. That is a an experimental change... push mbarbin github
99.36
129 main Enable 5.5 in CI push mbarbin github
99.36
128 main Prepare file for future 5.5 CI (currently unused) push mbarbin github
99.36
127 main Upgrade deploy-pages (node 24 warning) push mbarbin github
99.36
126 main Upgrade CIs push mbarbin github
99.36
See All Builds (125)

Badge your Repo: fpath-base

We detected this repo isn’t badged! Grab the embed code to the right, add it to your repo to show off your code coverage, and when the badge is live hit the refresh button to remove this message.
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

Refresh