Subject: Re: [boost] [builds] broken
From: Tom Kent (lists_at_[hidden])
Date: 2017-03-06 12:19:15
On Sun, Mar 5, 2017 at 3:20 PM, Rene Rivera <grafikrobot_at_[hidden]> wrote:
> On Sun, Mar 5, 2017 at 2:20 PM, Tom Kent <lists_at_[hidden]> wrote:
>
>>
>> Yeah, the specific runner I'm looking at at the moment has python, both 2
>> (2.7.6) and 3 (3.4.3, despite what the summary page says under the python
>> versions):
>> http://www.boost.org/development/tests/develop/developer/summary.html
>>
>> If you want to try that config yourself, you can get it from docker hub:
>> teeks99/boost-build:gcc-6
>>
>> I verified that it was getting the latest commit from develop:
>> 6abf48add87c66a7b118d0bc5e24ae045ba6fbb0
>>
>> Also, I noticed that there are two errors. The end of the output looks
>> like:
>>
>> warning: toolset gcc initialization: can not find tool windres
>> warning: initialized from /home/boost/user-config.jam:11
>> notice: using rc compiler :: <toolset>gcc-6~c++1z~warn :: /usr/bin/as
>> notice: [python-cfg] Configuring python...
>> notice: [python-cfg] user-specified version: "2.7"
>> notice: [python-cfg] user-specified includes: "/usr/include/python2.7"
>> notice: [python-cfg] user-specified libraries:
>> "/usr/lib/x86_64-linux-gnu"
>> notice: [python-cfg] Checking interpreter command "python2.7"...
>> notice: [python-cfg] running command 'python2.7 -c "from sys import *;
>> print('version=%d.%d\nplatform=%s\nprefix=%s\nexe
>> c_prefix=%s\nexecutable=%s' % (version_info[0],version_info[
>> 1],platform,prefix,exec_prefix,executable))" 2>&1'
>> notice: [python-cfg] ...requested configuration matched!
>> notice: [python-cfg] Details of this Python configuration:
>> notice: [python-cfg] interpreter command: "python2.7"
>> notice: [python-cfg] include path: "/usr/include/python2.7"
>> notice: [python-cfg] library path: "/usr/lib/x86_64-linux-gnu"
>> notice: [python-cfg] Checking for NumPy...
>> notice: [python-cfg] running command 'python2.7 -c "import sys;
>> sys.stderr = sys.stdout; import numpy; print(numpy.get_i
>> nclude())"'
>> notice: [python-cfg] NumPy disabled. Reason:
>> notice: [python-cfg] python2.7 -c "import sys; sys.stderr = sys.stdout;
>> import numpy; print(numpy.get_include())" abor
>> ted with
>> notice: [python-cfg] Traceback (most recent call last):
>> File "<string>", line 1, in <module>
>> ImportError: No module named numpy
>> notice: [python-cfg] Configuring python...
>> notice: [python-cfg] user-specified version: "3.4"
>> notice: [python-cfg] user-specified includes: "/usr/include/python3.4"
>> notice: [python-cfg] user-specified libraries:
>> "/usr/lib/x86_64-linux-gnu"
>> notice: [python-cfg] Checking interpreter command "python3.4"...
>> notice: [python-cfg] running command 'python3.4 -c "from sys import *;
>> print('version=%d.%d\nplatform=%s\nprefix=%s\nexe
>> c_prefix=%s\nexecutable=%s' % (version_info[0],version_info[
>> 1],platform,prefix,exec_prefix,executable))" 2>&1'
>> notice: [python-cfg] ...requested configuration matched!
>> notice: [python-cfg] Details of this Python configuration:
>> notice: [python-cfg] interpreter command: "python3.4"
>> notice: [python-cfg] include path: "/usr/include/python3.4"
>> notice: [python-cfg] library path: "/usr/lib/x86_64-linux-gnu"
>> notice: [python-cfg] Checking for NumPy...
>> notice: [python-cfg] running command 'python3.4 -c "import sys;
>> sys.stderr = sys.stdout; import numpy; print(numpy.get_i
>> nclude())"'
>> notice: [python-cfg] ...requested configuration matched!
>> notice: [python-cfg] Details of this Python configuration:
>> notice: [python-cfg] interpreter command: "python3.4"
>> notice: [python-cfg] include path: "/usr/include/python3.4"
>> notice: [python-cfg] library path: "/usr/lib/x86_64-linux-gnu"
>> notice: [python-cfg] Checking for NumPy...
>> notice: [python-cfg] running command 'python3.4 -c "import sys;
>> sys.stderr = sys.stdout; import numpy; print(numpy.get_i
>> nclude())"'
>> notice: [python-cfg] NumPy disabled. Reason:
>> notice: [python-cfg] python3.4 -c "import sys; sys.stderr = sys.stdout;
>> import numpy; print(numpy.get_include())" abor
>> ted with
>> notice: [python-cfg] Traceback (most recent call last):
>> File "<string>", line 1, in <module>
>> ImportError: No module named 'numpy'
>> notice: [zlib] Using pre-installed library
>> notice: [zlib] Condition
>> notice: [bzip2] Using pre-installed library
>> notice: [bzip2] Condition
>> Performing configuration checks
>>
>
> That very helpful :-)
>
>
>> - 32-bit : no
>> - 64-bit : yes
>> - arm : no
>> - mips1 : no
>> - power : no
>> - sparc : no
>> - x86 : yes
>> - symlinks supported : yes
>> ...found 1067 targets...
>> # Starting tests ("/var/boost/run/boost_bb/src/engine/bin.linuxx86_64/b2"
>> "-sBOOST_BUILD_PATH=/var/boost/run:/var/boost/
>> run/boost_bb/src" "-sBOOST_ROOT=/var/boost/run/boost_root"
>> "--boost=/var/boost/run/boost_root" "--boost-root=/var/boost/
>> run/boost_root" "--boost-build=/var/boost/run/boost_bb/src"
>> "--debug-configuration" -l300 toolset=gcc-6~c++1z -d2 prese
>> rve-test-targets=off --dump-tests -j8 address-model=64
>> --remove-test-targets -m64 "--build-dir=/var/boost/run/results" >
>> >"/var/boost/run/results/bjam.log" 2>&1)...
>> # Running Boost.Build tests
>> Traceback (most recent call last):
>> File "run.py", line 71, in <module>
>> runner(root)
>> File "/var/boost/run/boost_regression_src/regression.py", line 287, in
>> __init__
>> self.main()
>> File "/var/boost/run/boost_regression_src/regression.py", line 624, in
>> main
>> getattr(self,action_m)()
>> File "/var/boost/run/boost_regression_src/regression.py", line 589, in
>> command_regression
>> self.command_test()
>> File "/var/boost/run/boost_regression_src/regression.py", line 368, in
>> command_test
>> self.command_test_boost_build()
>> File "/var/boost/run/boost_regression_src/regression.py", line 410, in
>> command_test_boost_build
>> "boost/bin.v2/libs/any/test/any_test.test"));
>> OSError: [Errno 2] No such file or directory:
>> '/var/boost/run/results/boost/bin.v2/libs/any/test/any_test.test'
>>
>
> Interesting.. But unrelated AFAIK. The b2 tests rely on that any_test for
> a sanity check. So perhaps the test is gone and we need to use some other
> sanity check test.
>
> While the end of the results/bjam.log is:
>> error: Unable to find file or target named
>> error: '/boost/python//boost_numpy'
>> error: referred to from project at
>> error: '../libs/python/test'
>>
>> Hope that helps,
>>
>
> It does help. It's fixed now, as that target should always exist.
>
Things seem to be running again, thanks!
I'll put adding numpy to some of my runners on my task list.
Tom