input-output-hk / constrained-generators
77%

DEFAULT BRANCH: master
Repo Added
Files 33
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 master
branch: SELECT
CHANGE BRANCH
x

coverage: 77.357% (+0.02%) from 77.337%
Relevant lines Covered
5198 RELEVANT LINES 4021 COVERED LINES
1.46 HITS PER LINE
Source Files on master

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
537 master Resolve nightly failures (#74) The reason for removing the benchmarks is: Criterion build broke, and (more importantly) The benchmarks weren't used in any meanigful way anyway. When doing any performance work I'd just default to running a given ... push web-flow github
77.36
536 master Resolve nightly failures (#74) The reason for removing the benchmarks is: Criterion build broke, and (more importantly) The benchmarks weren't used in any meanigful way anyway. When doing any performance work I'd just default to running a given ... push web-flow github
77.36
535 master Resolve nightly failures (#74) The reason for removing the benchmarks is: Criterion build broke, and (more importantly) The benchmarks weren't used in any meanigful way anyway. When doing any performance work I'd just default to running a given ... push web-flow github
77.3
534 master Resolve nightly failures (#74) The reason for removing the benchmarks is: Criterion build broke, and (more importantly) The benchmarks weren't used in any meanigful way anyway. When doing any performance work I'd just default to running a given ... push web-flow github
77.38
533 master Resolve nightly failures (#74) The reason for removing the benchmarks is: Criterion build broke, and (more importantly) The benchmarks weren't used in any meanigful way anyway. When doing any performance work I'd just default to running a given ... push web-flow github
77.34
532 master Resolve nightly failures (#74) The reason for removing the benchmarks is: Criterion build broke, and (more importantly) The benchmarks weren't used in any meanigful way anyway. When doing any performance work I'd just default to running a given ... push web-flow github
77.36
531 master Resolve nightly failures (#74) The reason for removing the benchmarks is: Criterion build broke, and (more importantly) The benchmarks weren't used in any meanigful way anyway. When doing any performance work I'd just default to running a given ... push web-flow github
77.3
530 master Resolve nightly failures (#74) The reason for removing the benchmarks is: Criterion build broke, and (more importantly) The benchmarks weren't used in any meanigful way anyway. When doing any performance work I'd just default to running a given ... push web-flow github
77.4
529 master Resolve nightly failures (#74) The reason for removing the benchmarks is: Criterion build broke, and (more importantly) The benchmarks weren't used in any meanigful way anyway. When doing any performance work I'd just default to running a given ... push web-flow github
77.34
528 master Resolve nightly failures (#74) The reason for removing the benchmarks is: Criterion build broke, and (more importantly) The benchmarks weren't used in any meanigful way anyway. When doing any performance work I'd just default to running a given ... push web-flow github
77.36
See All Builds (205)