Travis log output stops at random spots in the middle of a `byte-compiling` stage

In our build, we consistently get something like the following:

byte-compiling build/bdist.linux-aarch64/egg/pip/_internal/commands/hash.py to hash.cpython-37.pyc

byte-compiling build/bdist.linux-aarch64/egg/pip/_internal/commands/help.py to help.cpython-37.pyc

byte-compiling build/bdist.linux-aarch64/egg/pip/_internal/commands/check.py to check.cpython-37.

No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.

Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received

This is in the middle of a pip install command. Every time we retriggered the build, it got stuck in a different spot. This started happening a couple of days ago on our previously passing builds, and has been happening on all ARM boards across our repos with PRs that make very minor changes. Could anyone help us, please? Thanks in advance.

Happening to us on cdr/code-server as well.

Please fix this travis!

The bug has actually gone away yesterday for us. You might wanna retrigger your build.

Still happening to us, all day today and yesterday :frowning:

Imprint