Print fewer download updates in headless mode

[HebaruSan]

Problem

When GPP updates, Jenkins has to download 181 MB of files. Since Cmdline currently prints a download status every 3 seconds, this results in most of the log looking like this:

https://ci.ksp-ckan.org/job/NetKAN/6759/consoleText

1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           
1615 kbps - downloading - 98 MB left - 45%           

This time it went on for 15060 lines, and a total of 827 kilobytes, almost all of which is just clutter.

Changes

Now when netkan or ckan are running in headless mode, which Jenkins uses, they will only print a download progress update when the percentage changes (or less often, for very fast downloads). This will limit the number of lines to at most 100 while still logging the download.

I didn't reduce the number of updates coming from Core because these can be appropriate for making it clear that the GUI is still running.

[HebaruSan]

Did we run out of CPU time on Travis?

[techman83]

According to the status page:

Update - We are still investigating the job backlog incident.
Jan 17, 00:26 UTC

Current time is 00:34 UTC

[HebaruSan]

Ahh interesting, it never occurred to me that they might be having an outage. Well now I can just watch that page. Thanks!