Bad display of console progress bars in gitlab-ci web interface
Summary
I'm using wget
in gitlab-ci
to make an Anaconda-python environment to test my code. The problem is that the output of wget
is messy, as you can see below: the progress bars in the console output of gitlab-ci
are badly displayed, and clutter the output.
Steps to reproduce
It happens using wget
or other commands displaying progress bars within .gitlab-ci.yml
Expected behavior
Something like the good old
downloading: TheFile.tar.gz ...
--09:30:42-- http://somesite.com/TheFile.jpeg
=> `/home/me/Downloads/TheFile.jpeg'
Resolving somesite.co... xxx.xxx.xxx.xxx.
Connecting to somesite.co|xxx.xxx.xxx.xxx|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1,614,820 (1.5M) [image/jpeg]
25% [======> ] 614,424 173.62K/s ETA 00:14
Relevant logs and/or screenshots
Using wget
, I...get:
$ wget https://repo.continuum.io/miniconda/Miniconda3-latest-Linux-x86_64.sh -O miniconda.sh
converted 'https://repo.continuum.io/miniconda/Miniconda3-latest-Linux-x86_64.sh' (ANSI_X3.4-1968) -> 'https://repo.continuum.io/miniconda/Miniconda3-latest-Linux-x86_64.sh' (UTF-8)
--2016-02-02 07:33:11-- https://repo.continuum.io/miniconda/Miniconda3-latest-Linux-x86_64.sh
Resolving repo.continuum.io (repo.continuum.io)... 50.17.212.245, 107.21.238.156
Connecting to repo.continuum.io (repo.continuum.io)|50.17.212.245|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 31089707 (30M) [application/octet-stream]
Saving to: 'miniconda.sh'
0K .......... .......... .......... .......... .......... 0% 2.22M 13s
50K .......... .......... .......... .......... .......... 0% 3.88M 10s
100K .......... .......... .......... .......... .......... 0% 2.90M 10s
150K .......... .......... .......... .......... .......... 0% 4.52M 9s
200K .......... .......... .......... .......... .......... 0% 4.34M 9s
250K .......... .......... .......... .......... .......... 0% 4.56M 8s
300K .......... .......... .......... .......... .......... 1% 4.38M 8s
350K .......... .......... .......... .......... .......... 1% 4.36M 8s
400K .......... .......... .......... .......... .......... 1% 10.7M 7s
450K .......... .......... .......... .......... .......... 1% 6.04M 7s
500K .......... .......... .......... .......... .......... 1% 4.41M 7s
550K .......... .......... .......... .......... .......... 1% 4.40M 7s
and using conda
package manager I get:
$ conda install numpy pytest
Fetching package metadata: ....
Solving package specifications: ........................
Package plan for installation in environment /root/miniconda:
The following packages will be downloaded:
package | build
---------------------------|-----------------
libgfortran-1.0 | 0 170 KB
openblas-0.2.14 | 3 3.5 MB
numpy-1.10.2 | py35_0 5.8 MB
py-1.4.31 | py35_0 126 KB
pytest-2.8.5 | py35_0 225 KB
------------------------------------------------------------
Total: 9.7 MB
The following NEW packages will be INSTALLED:
libgfortran: 1.0-0
numpy: 1.10.2-py35_0
openblas: 0.2.14-3
py: 1.4.31-py35_0
pytest: 2.8.5-py35_0
Fetching packages ...
libgfortran-1. 0% | | ETA: --:--:-- 0.00 B/slibgfortran-1. 9% |## | ETA: 0:00:00 2.79 MB/slibgfortran-1. 18% |##### | ETA: 0:00:00 2.71 MB/slibgfortran-1. 28% |######## | ETA: 0:00:00 3.62 MB/slibgfortran-1. 37% |########### | ETA: 0:00:00 3.54 MB/slibgfortran-1. 47% |############## | ETA: 0:00:00 4.31 MB/slibgfortran-1. 56% |################# | ETA: 0:00:00 4.87 MB/slibgfortran-1. 65% |#################### | ETA: 0:00:00 4.55 MB/slibgfortran-1. 75% |####################### | ETA: 0:00:00 5.09 MB/slibgfortran-1. 84% |########################## | ETA: 0:00:00 5.62 MB/slibgfortran-1. 94% |############################# | ETA: 0:00:00 5.25 MB/slibgfortran-1. 100% |###############################| ETA: 0:00:00 5.50 MB/slibgfortran-1. 100% |###############################| Time: 0:00:00 5.44 MB/s
openblas-0.2.1 0% | | ETA: --:--:-- 0.00 B/sopenblas-0.2.1 0% | | Time: 0:00:00 2.70 MB/sopenblas-0.2.1 0% | | Time: 0:00:00 2.54 MB/sopenblas-0.2.1 1% | | Time: 0:00:00 3.69 MB/sopenblas-0.2.1 1% | | Time: 0:00:00 3.40 MB/sopenblas-0.2.1 2% | | Time: 0:00:00 4.16 MB/sopenblas-0.2.1 2% | | Time: 0:00:00 3.83 MB/sopenblas-0.2.1 3% | | Time: 0:00:00 4.39 MB/sopenblas-0.2.1 3% |# | Time: 0:00:00 4.95 MB/sopenblas-0.2.1 4% |# | Time: 0:00:00 4.59 MB/sopenblas-0.2.1 4% |# | Time: 0:00:00 5.04 MB/sopenblas-0.2.1 4% |# | Time: 0:00:00 5.40 MB/sopenblas-0.2.1 5% |# | Time: 0:00:00 5.81 MB/sopenblas-0.2.1 5% |# | Time: 0:00:00 5.35 MB/sopenblas-0.2.1 6% |# | Time: 0:00:00 5.70 MB/sopenblas-0.2.1 6% |## | Time: 0:00:00 5.95 MB/sopenblas-0.2.1 7% |## | Time: 0:00:00 6.29 MB/sopenblas-0.2.1 7% |## | Time: 0:00:00 6.03 MB/sopenblas-0.2.1 8% |## | Time: 0:00:00 6.28 MB/sopenblas-0.2.1 8% |## | Time: 0:00:00 6.57 MB/sopenblas-0.2.1 9% |## | Time: 0:00:00 6.76 MB/sopenblas-0.2.1 9% |## | Time: 0:00:00 7.04 MB/sopenblas-0.2.1 9% |### | Time: 0:00:00 6.84 MB/sopenblas-0.2.1 10% |### | Time: 0:00:00 7.08 MB/sopenblas-0.2.1 10% |### | Time: 0:00:00 7.33 MB/sopenblas-0.2.1 11% |### | Time: 0:00:00 7.58 MB/sopenblas-0.2.1 11% |### | Time: 0:00:00 7.69 MB/sopenblas-0.2.1 12% |###
Possible fixes
no idea...
Edited by Jason Yavorska