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

fhunleth / fwup / 1217 / 4
86%
master: 86%

Build:
DEFAULT BRANCH: master
Ran 19 Sep 2019 10:54AM UTC
Files 485
Run time 17s
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

19 Sep 2019 10:50AM UTC coverage: 85.868% (+0.03%) from 85.84%
MODE=dynamic

push

travis-ci

fhunleth
Make it more obvious that progress only goes up

While it's possible to trace the code and verify that progress can only
move upward, making the progress reporting code check too makes this
easier to convey to others. The hope is that it will be easier to defend
fwup in the future the next time someone thinks that its progress
reports went down.

In case it happens again and this commit message is seen, the cause of
progress reports "going down" was due to a UI re-sorting a device
listing that had several devices updating simultaneously. Visually, two
or more rows switched order and it looked as if one device's progress
was going down. However, on closer inspection, it was clear that device
ordering was changing and that update progress never went the wrong way.

3032 of 3531 relevant lines covered (85.87%)

27934.78 hits per line

Source Files on job 1217.4 (MODE=dynamic)
  • Tree
  • List 0
  • Changed 18
  • Source Changed 4
  • Coverage Changed 16
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 1180
  • Travis Job 1217.4
  • f653a3fa on github
  • Prev Job for MODE=dynamic on master (#1212.4)
  • Next Job for MODE=dynamic on master (#1234.4)
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