Opened at 2014-12-26T22:55:48Z
Closed at 2019-07-25T13:11:43Z
#2355 closed defect (wontfix)
on one occasion, travis-ci timed out because a pycryptopp compile took > 10 minutes
Reported by: | zooko | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | undecided |
Component: | dev-infrastructure | Version: | 1.10.0 |
Keywords: | pycryptopp | Cc: | |
Launchpad Bug: |
Description
This build failed due to an error:
https://travis-ci.org/tahoe-lafs/tahoe-lafs/jobs/45180843
The end of the log says:
Need pycryptopp>=0.6.0 Searching for pycryptopp>=0.6.0 Reading http://pypi.python.org/simple/pycryptopp/ Best match: pycryptopp 0.6.0.1206569328141510525648634803928199668821045408958 Downloading https://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-sdists/pycryptopp-0.6.0.1206569328141510525648634803928199668821045408958.tar.gz Processing pycryptopp-0.6.0.1206569328141510525648634803928199668821045408958.tar.gz Running pycryptopp-0.6.0.1206569328141510525648634803928199668821045408958/setup.py -q bdist_egg --dist-dir /tmp/easy_install-UNNTmx/pycryptopp-0.6.0.1206569328141510525648634803928199668821045408958/egg-dist-tmp-vJr5IQ cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for Ada/C/ObjC but not for C++ [enabled by default] cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for Ada/C/ObjC but not for C++ [enabled by default] cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for Ada/C/ObjC but not for C++ [enabled by default] cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for Ada/C/ObjC but not for C++ [enabled by default] cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for Ada/C/ObjC but not for C++ [enabled by default] cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for Ada/C/ObjC but not for C++ [enabled by default] cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for Ada/C/ObjC but not for C++ [enabled by default] cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for Ada/C/ObjC but not for C++ [enabled by default] cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for Ada/C/ObjC but not for C++ [enabled by default] cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for Ada/C/ObjC but not for C++ [enabled by default] cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for Ada/C/ObjC but not for C++ [enabled by default] cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for Ada/C/ObjC but not for C++ [enabled by default] cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for Ada/C/ObjC but not for C++ [enabled by default] cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for Ada/C/ObjC but not for C++ [enabled by default] cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for Ada/C/ObjC but not for C++ [enabled by default] cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for Ada/C/ObjC but not for C++ [enabled by default] cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for Ada/C/ObjC but not for C++ [enabled by default] No output has been received in the last 10 minutes, this potentially indicates a stalled build or something wrong with the build itself. The build has been terminated
My guess is that it takes longer than 10 minutes to build pycryptopp on the travis-ci machine.
Change History (3)
comment:1 in reply to: ↑ description Changed at 2014-12-26T23:11:09Z by daira
comment:2 Changed at 2014-12-26T23:13:12Z by daira
- Summary changed from travis-ci times out because pycryptopp compile takes > 10 minutes to on one occasion, travis-ci timed out because a pycryptopp compile took > 10 minutes
comment:3 Changed at 2019-07-25T13:11:43Z by exarkun
- Resolution set to wontfix
- Status changed from new to closed
ticket:3031 switched Tahoe-LAFS from pycryptopp to cryptography.
Note: See
TracTickets for help on using
tickets.
Replying to zooko:
In this Travis job, the entire build including building pycryptopp took only 142 seconds. So something unusual must have gone wrong in the job you cited.