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

daviddrysdale / c-ares / 200 / 3
89%
master: 89%

Build:
DEFAULT BRANCH: master
Ran 11 Mar 2016 11:12AM UTC
Files 251
Run time 8s
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

09 Mar 2016 02:10PM UTC coverage: 95.369%. Remained the same
BUILD_TYPE=coverage

push

travis-ci

Daniel Stenberg
configure: check if tests can get built before enabled

The current approach for disabling tests is not a good solution because
it forces you to pass --disable-tests, rather than auto-detect if your
system can support the tests in the first place.  Many (most?) systems
do not have C++11.  This also causes issues when chain-building c-ares,
the hosting system needs to be updated to support passing this
additional flag if necessary, it doesn't seem reasonable to add this
requirement which breaks compatibility.

This change auto-detects if the system can build the tests and
automatically disable them if it cannot.  If you pass --enable-tests to
configure and the system cannot build them either due to lack of system
support, or because cross-compilation is being used, it will throw an
appropriate error since the user indicated they really did want the
tests.

3604 of 3779 relevant lines covered (95.37%)

3550.01 hits per line

Source Files on job 200.3 (BUILD_TYPE=coverage)
  • Tree
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 200
  • Travis Job 200.3
  • c64a374a on github
  • Prev Job for BUILD_TYPE=coverage on master (#194.3)
  • Next Job for BUILD_TYPE=coverage on master (#201.3)
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