• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

letsencrypt / ct-woodpecker / 164 / 1
69%
main: 68%

Build:
Build:
LAST BUILD BRANCH: master
DEFAULT BRANCH: main
Ran 21 Jun 2018 07:18PM UTC
Files 9
Run time 1s
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

21 Jun 2018 07:16PM UTC coverage: 66.209% (-2.5%) from 68.694%
164.1

push

travis-ci

web-flow
Integration tests: relax testing requirements. (#30)

Previously the ct-woodpecker integration tests were a bit
flaky. The root cause is our usage of elapsed ct-woodpecker runtime as
a proxy for work completed. This is hard to do with accuracy. As
one example, the time required to fetch metrics output before stopping
the ct-woodpecker instance could result in another sth fetch/cert submit
cycle happening before the test completes, causing miscounts of expected
operations.

This commit changes the tests to just ensure a minimum of 1 cycles worth
of work (plus the startup cycle) occurs during testing. This is Good
Enough and will save us from considerable headaches tweaking padding
timeouts or overcomplicating the design of ct-woodpecker to expose cycle
information back to the test rig.

This commit also adds clean shutdown code to the monitors. This prevents
ghost monitor goroutines from sticking around when the parent
ct-woodpecker is stopped.

386 of 583 relevant lines covered (66.21%)

4.35 hits per line

Source Files on job 164.1
  • Tree
  • List 0
  • Changed 5
  • Source Changed 4
  • Coverage Changed 5
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 86
  • Travis Job 164.1
  • 5429cb93 on github
  • Prev Job for on master (#159.1)
  • Next Job for on master (#167.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc