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.299% (-0.04%) from 77.337%
Relevant lines Covered
5198 RELEVANT LINES 4018 COVERED LINES
1.46 HITS PER LINE
Source Files on master

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
556 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
555 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.32
554 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
553 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
552 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
551 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
550 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
549 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
548 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.32
547 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.32
See All Builds (224)