"Build output is too large..." due to capturing `pip install ...` progress

Feedback & Bug Reports
, ,
1 
Python 3.6.1
Collecting numpy>=1.9.0 (from -r requirements.txt (line 1))
  Downloading numpy-1.14.2-cp36-cp36m-manylinux1_x86_64.whl (12.2MB)

    0% |                                | 10kB 32.0MB/s eta 0:00:01
    0% |                                | 20kB 18.3MB/s eta 0:00:01
    0% |                                | 30kB 23.0MB/s eta 0:00:01
    0% |                                | 40kB 17.3MB/s eta 0:00:01
    0% |â–Ź                               | 51kB 15.6MB/s eta 0:00:01
    0% |â–Ź                               | 61kB 17.7MB/s eta 0:00:01
    0% |â–Ź                               | 71kB 16.5MB/s eta 0:00:01
    0% |â–Ź                               | 81kB 17.9MB/s eta 0:00:01
    0% |â–Ž                               | 92kB 15.7MB/s eta 0:00:01
    0% |â–Ž                               | 102kB 14.9MB/s eta 0:00:01
    0% |â–Ž                               | 112kB 15.2MB/s eta 0:00:01
    1% |â–Ž                               | 122kB 15.9MB/s eta 0:00:01
    1% |â–Ť                               | 133kB 15.1MB/s eta 0:00:01
    1% |â–Ť                               | 143kB 17.2MB/s eta 0:00:01
    1% |â–Ť                               | 153kB 17.3MB/s eta 0:00:01
    1% |â–Ť                               | 163kB 17.3MB/s eta 0:00:01
    1% |â–Ś                               | 174kB 19.1MB/s eta 0:00:01
    1% |â–Ś                               | 184kB 16.4MB/s eta 0:00:01
    1% |â–Ś                               | 194kB 19.9MB/s eta 0:00:01
    1% |â–Ś                               | 204kB 23.0MB/s eta 0:00:01
    1% |â–‹                               | 215kB 21.0MB/s eta 0:00:01
    1% |â–‹                               | 225kB 22.4MB/s eta 0:00:01
    1% |â–‹                               | 235kB 23.7MB/s eta 0:00:01

Etc…

2

What’s your question? :smiley_cat:

3

I see it as a bug that the progress bars are captured as line by line components in the main web interface. The web interface should minimize user impedance of analyzing build logs. Downloading the raw log shouldn’t be a workflow requirement. The web interface of similar CI services (Travis, GitLab, etc) do not suffer from this issue.

So this leads to two questions:

  1. Are there any user commands/configurations that would prevent this?
  2. Are there service/server-side fixes that would resolve this issue?
4

These sorts of progress bars are done in the same way in a variety of applications - they use libraries to output control characters to manipulate the cursor position, then overwrite screen contents.

I personally don’t think it’s a CI responsibility to parse this stuff - it is better to get rid of the progress bar (it probably isn’t very useful as a log output anyway). Does your installer script have a quiet mode?

5

Issue reported here, found with this search. A solution can be found at the end of that bug report.

1 Like
6

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.