Your message dated Sat, 22 Nov 2014 12:50:24 +0100 with message-id <1416657024.5151.3.ca...@debian.org> and subject line not reproducible with latest pbuilder has caused the Debian Bug report #770071, regarding cpp-netlib: FTBFS under pbuilder: Test failure to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 770071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770071 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: cpp-netlib Version: 0.11.0-1.1 Severity: serious >From my pbuilder build log (on amd64): ... dh_auto_test -Nlibcppnetlib-doc make[1]: Entering directory '/tmp/buildd/cpp-netlib-0.11.0/obj-x86_64-linux-gnu' Running tests... /usr/bin/ctest --force-new-ctest-process -j1 Test project /tmp/buildd/cpp-netlib-0.11.0/obj-x86_64-linux-gnu Start 1: cpp-netlib-message_test 1/16 Test #1: cpp-netlib-message_test ............................. Passed 0.33 sec Start 2: cpp-netlib-message_transform_test 2/16 Test #2: cpp-netlib-message_transform_test ................... Passed 0.05 sec Start 3: cpp-netlib-utils_thread_pool 3/16 Test #3: cpp-netlib-utils_thread_pool ........................ Passed 0.01 sec Start 4: cpp-netlib-uri_test 4/16 Test #4: cpp-netlib-uri_test ................................. Passed 0.01 sec Start 5: cpp-netlib-uri_builder_test 5/16 Test #5: cpp-netlib-uri_builder_test ......................... Passed 0.04 sec Start 6: cpp-netlib-uri_builder_stream_test 6/16 Test #6: cpp-netlib-uri_builder_stream_test .................. Passed 0.01 sec Start 7: cpp-netlib-uri_encoding_test 7/16 Test #7: cpp-netlib-uri_encoding_test ........................ Passed 0.01 sec Start 8: cpp-netlib-relative_uri_test 8/16 Test #8: cpp-netlib-relative_uri_test ........................ Passed 0.01 sec Start 9: cpp-netlib-http-request_incremental_parser_test 9/16 Test #9: cpp-netlib-http-request_incremental_parser_test ..... Passed 0.01 sec Start 10: cpp-netlib-http-request_linearize_test 10/16 Test #10: cpp-netlib-http-request_linearize_test .............. Passed 0.01 sec Start 11: cpp-netlib-http-client_constructor_test 11/16 Test #11: cpp-netlib-http-client_constructor_test ............. Passed 0.01 sec Start 12: cpp-netlib-http-client_get_timeout_test 12/16 Test #12: cpp-netlib-http-client_get_timeout_test .............***Exception: SegFault 0.13 sec terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::thread_resource_error> >' what(): boost thread: trying joining itself: Resource deadlock avoided Running 12 test cases... Start 13: cpp-netlib-http-server_constructor_test 13/16 Test #13: cpp-netlib-http-server_constructor_test ............. Passed 0.01 sec Start 14: cpp-netlib-http-server_async_run_stop_concurrency 14/16 Test #14: cpp-netlib-http-server_async_run_stop_concurrency ... Passed 1.31 sec Start 15: cpp-netlib-http-server_header_parser_test 15/16 Test #15: cpp-netlib-http-server_header_parser_test ........... Passed 0.00 sec Start 16: mime-roundtrip 16/16 Test #16: mime-roundtrip ...................................... Passed 0.19 sec 94% tests passed, 1 tests failed out of 16 Total Test time (real) = 2.24 sec The following tests FAILED: 12 - cpp-netlib-http-client_get_timeout_test (SEGFAULT) Errors while running CTest Makefile:120: recipe for target 'test' failed make[1]: *** [test] Error 8 make[1]: Leaving directory '/tmp/buildd/cpp-netlib-0.11.0/obj-x86_64-linux-gnu' dh_auto_test: make -j1 test ARGS+=-j1 returned exit code 2 debian/rules:19: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 This looks like it might be related to the fact that pbuilder now totally disables network access, except for a new instance of lo. -- Daniel Schepler
--- End Message ---
--- Begin Message ---Source: cpp-netlib Version: 0.11.0-1.1 Hi, on two machines (amd64, i386), I could not reproduce this bug with the latest pbuilder release (0.215+nmu3), which enables lo interface again. Therefore I close this bug. If I disable lo by hand, the test never stopped (more exactly, I killed it after some minutes). Best wishes, Johann Felix
--- End Message ---
