question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Progress bar bug breaks torch installation on Travis CI

See original GitHub issue

Environment

  • pip version: 18.1
  • Python version: 3.5.6, 3.6.7, 3.7.1
  • OS: Ubuntu Xenial
  • CI: Travis

Description

Installing torch with pip on Travis CI results in the following error:

Collecting torch>=0.4 (from -r requirements.txt (line 7)) Downloading https://files.pythonhosted.org/packages/f5/3b/0b8de6e654c2983898564226792c6f09d9bcaba97b7b29c40e4ed4ae43ed/torch-1.0.0-cp37-cp37m-manylinux1_x86_64.whl (591.8MB) 73% |███████████████████████▌ | 434.3MB 36.8MB/s eta 0:00:05 The job exceeded the maximum log length, and has been terminated.

Expected behavior

This shouldn’t be problematic. All other Python dependencies were successfully installed via pip on Travis CI.

How to Reproduce

  1. Create an empty GitHub repository
  2. Add a .travis.yml file that tries to pip install torch during the install phase
  3. Add Travis CI via GitHub Apps integration and initiate a build

Output

One of the times I submitted, I got lucky and saw the following log: screen shot 2018-12-28 at 4 34 00 pm It appears that there is a bug in the progress bar. This may only affect very large downloads like torch.

Known Workarounds

The following workaround solved the problem for me:

$ pip install --progress-bar off ...

It would be good to get the progress bar fixed though.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:1
  • Comments:7 (3 by maintainers)

github_iconTop GitHub Comments

3reactions
native-apicommented, Dec 29, 2018

The progress bar output in the Travis log looks just as “broken” for other downloads, too. The only difference is they don’t take as long, so the amount of garbage in the log is insufficient to go over the log size limit.

0reactions
lock[bot]commented, May 30, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Common Build Problems - Travis CI Docs
A very common cause when a test is suddenly breaking without any major code changes involved is a change in upstream dependencies.
Read more >
Large pip installs exceed maximum log length - Python
it disables the progress bar, the maximum log length isn't exceeded, and the build successfully completes. This is likely a bug in pip...
Read more >
pipenv Documentation - Read the Docs
Generates and checks file hashes for locked dependencies when installing from Pipfile.lock. • Automatically install required Python version when pyenv is ...
Read more >
Introduction — AxonDeepSeg 3.2.0 documentation
AxonDeepSeg is an open-source software using deep learning and aiming at automatically segmenting axons and myelin sheaths from microscopy images. It performs 3 ......
Read more >
Untitled
Karl-wilhelm-platz, Travis picking wiki, L.a. confidential book! ... Arley hall airedales, Agaoglu insaat ankara, Circle progress bar android.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found