You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The way we report download progress in buildozer/__init__.py download() is absolutely helpful in the terminal, but really messes up with Travis logger.
When downloading things as big as the Android NDK via buildozer, it produces a very large amount of progress lines, like in the extract below:
To fix the issue, maybe we should make it possible to reduce the verbosity of this download() method. Other suggestions are very welcome.
Side note: same issue exists in p4a via download_file(), but the most annoying currently is buildozer as it generates lager downloads so far.
The text was updated successfully, but these errors were encountered:
The way we report download progress in
buildozer/__init__.py
download() is absolutely helpful in the terminal, but really messes up with Travis logger.When downloading things as big as the Android NDK via buildozer, it produces a very large amount of progress lines, like in the extract below:
In total this log file has over 100K lines of
- Download
! See attached screenshot and complete log for reference: https://api.travis-ci.org/v3/job/491113892/log.txtTo fix the issue, maybe we should make it possible to reduce the verbosity of this
download()
method. Other suggestions are very welcome.Side note: same issue exists in p4a via
download_file()
, but the most annoying currently isbuildozer
as it generates lager downloads so far.The text was updated successfully, but these errors were encountered: