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

brailcom / pytis / 216 / 3
34%
master: 34%

Build:
DEFAULT BRANCH: master
Ran 08 Sep 2016 08:27AM UTC
Files 106
Run time 6s
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

08 Sep 2016 08:04AM UTC coverage: 35.171%. Remained the same
PGVER=9.3

push

travis-ci

cerha
Fix `gensql` failures being unnoticed during CI

In shell pipe compound command, only the exit status of the last process
is the exit status of the whole compound command. So in case the last
command in the pipe exits with 0 status, the whole compound pipe command
will exit with 0 status (i.e. fine) even if previous commands in the
pipe errored with non-zero status. See
e.g. http://unix.stackexchange.com/questions/14270/get-exit-status-of-process-thats-piped-to-another

This could cause `gensql` errors to be unnoticed by the CI: `psql` did
not mind, as it got fed valid SQL and it cannot know that the SQL is
incomplete from the app logic point of view.

We now put `gensql` output into a file, and do not pipe it to `psql`.

15347 of 43636 relevant lines covered (35.17%)

0.35 hits per line

Source Files on job 216.3 (PGVER=9.3)
  • Tree
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 216
  • Travis Job 216.3
  • 57393e47 on github
  • Prev Job for PGVER=9.3 on master (#215.3)
  • Next Job for PGVER=9.3 on master (#217.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