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

zmwangx / storyboard / 86 / 7
90%
master: 90%

Build:
DEFAULT BRANCH: master
Ran 11 May 2015 05:00AM UTC
Files 7
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

11 May 2015 04:55AM UTC coverage: 90.317%. Remained the same
86.7

push

travis-ci

zmwangx
THE REAL 0.1.01

Marked PyPy2 build on Travis as allowed failure (then it actually
wouldn't fail). See the debugging process below for why.

---

Squashed commit of the following:

commit 36736c4e1
Author: Zhiming Wang <zmwangx@gmail.com>
Date:   Sun May 10 21:47:15 2015 -0700

    revert last two commits and drop pypy2

    The PyPy2 environment on Travis is just random:
    https://travis-ci.org/zmwangx/storyboard/jobs/62030653

commit 2d8a982f3
Author: Zhiming Wang <zmwangx@gmail.com>
Date:   Sun May 10 21:33:45 2015 -0700

    remove or rewrite print calls with explicit write calls

    There may or may not be a problem with capturing stdout in PyPy2 which
    randomly prevents proper printing. At least, I replaced a print calls
    with explicit write calls in the last commit, and now it's not failing:
    https://travis-ci.org/zmwangx/storyboard/jobs/62029848

    Hope this commit gets through, or I would be slapped in the face again.

commit 402b3cf59
Author: Zhiming Wang <zmwangx@gmail.com>
Date:   Sun May 10 21:18:56 2015 -0700

    replace print with sys.stdout.write

    just to see what happens.

    Interestingly, this time PyPy fails at a different place, still with
    nothing printed to stdout (presumably). Is there anything weird about
    PyPy2's stdout (that's makes it not so capturing-safe)? If it still
    fails this time, I might just drop PyPy2. There's no problem in PyPy3.

commit cafe2c408
Author: Zhiming Wang <zmwangx@gmail.com>
Date:   Sun May 10 21:02:29 2015 -0700

    frame.py: print stderr when ffmpeg emitted no frame

    Strangely enough, I only bumped the version number and removed allowed
    failure from .travis.yml and all of a sudden the build was failing on
    PyPy2, because FFmpeg failed to extract a frame!

    https://travis-ci.org/zmwangx/storyboard/jobs/62027392

970 of 1074 relevant lines covered (90.32%)

0.9 hits per line

Source Files on job 86.7
  • Tree
  • List 0
  • Changed 1
  • Source Changed 1
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 86
  • Travis Job 86.7
  • ea5f38ab on github
  • Prev Job for on master (#81.7)
  • Next Job for on master (#88.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