Ran
|
Jobs
1
|
Files
34
|
Run time
5s
|
Badge
Embed ▾
README BADGES
|
travis-ci
<a href="https://github.com/mbland/go-script-bash/commit/<a class=hub.com/mbland/go-script-bash/commit/<a class="double-link" href="https://git"><a class=hub.com/mbland/go-script-bash/commit/480bce3e64cfda362ac70c59364d0453403673d7">480bce3e6<a href="https://github.com/mbland/go-script-bash/commit/480bce3e64cfda362ac70c59364d0453403673d7"><a href="https://github.com/mbland/go-script-bash/commit/480bce3e64cfda362ac70c59364d0453403673d7">">core: Default to 80 columns on all tput errors Commit </a><a class="double-link" href="https://github.com/mbland/go-script-bash/commit/<a class="double-link" href="https://github.com/mbland/go-script-bash/commit/271c7269b2285ab37f71041ce97228614c5d93a2">271c7269b</a>">271c7269b</a><a href="https://github.com/mbland/go-script-bash/commit/480bce3e64cfda362ac70c59364d0453403673d7"> didn&#39;t fix the Travis build failure, per https://travis-ci.org/mbland/go-script-bash/jobs/174892711. This change should resolve it once and for all, though the test reproduces a tput error differently from whatever&#39;s happening on Travis. I&#39;m wondering if it&#39;s a transient issue, as the Travis logs aren&#39;t showing colorized output today, either. Notice the first line of yesterday&#39;s last passing build: https://travis-ci.org/mbland/go-script-bash/jobs/174681893 Using worker: worker-linux-docker-70d3e188.prod.travis-ci.org:travis-linux-4 The first failing build from this morning, which was due to a legitimate test failure, was similar: https://travis-ci.org/mbland/go-script-bash/jobs/174826033 The same was also true for: https://travis-ci.org/mbland/go-script-bash/jobs/174826656 Compare that to the first lines of the first failing build in this series: https://travis-ci.org/mbland/go-script-bash/jobs/174877411#L1-L5 Worker information hostname: i-3590adcd-precise-production-2-worker-org-docker.travisci.net:363acf18-6c52-4da0-8504-43f4ea7484c3 version: v2.5.0-8-g19ea9c2 https://github.com/travis-ci/worker/tree/</a><a class="double-link" href="https://github.com/mbland/go-script-bash/commit/<a class="double-link" href="https://github.com/mbland/go-script-bash/commit/19ea9c20425c78100500c7cc935892b47024922c">19ea9c204</a>">19ea9c204</a><a href="https://github.com/mbland/go-script-bash/commit/480bce3e64cfda362ac70c59364d0453403673d7"> instance: 3d7fc5b:travis:default startup: 1.191683692s So something definitely changed. Either way, the build should succeed regardless of $TERM and tput issues now.
12 of 12 new or added lines in 2 files covered. (100.0%)
1350 of 1402 relevant lines covered (96.29%)
105.35 hits per line
ID | Job ID | Ran | Files | Coverage | |
---|---|---|---|---|---|
1 | 162.1 | 34 |
96.29 |
Travis Job 162.1 |
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
---|