<div dir="ltr"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 20, 2019 at 7:15 AM Rene Rivera <<a href="mailto:grafikrobot@gmail.com">grafikrobot@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Since it's not due to the b2 -j change..</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jun 14, 2019 at 8:25 AM Tom Kent via Boost-Testing <<a href="mailto:boost-testing@lists.boost.org" target="_blank">boost-testing@lists.boost.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">For the last few days (Since June 4?) I've been having problems with all my linux tests running against the develop branch. <div><br></div><div>GCC ends with this:<br><br><span style="font-family:monospace"><span style="color:rgb(0,0,0)">gcc.compile.c++ ../../bin/common/build/gcc-8/release/process_jam_log.o
</span><br>
<br> "g++-8" -fPIC -O3 -finline-functions -Wno-inline -Wall -DBOOST_ALL_NO_LIB=1 -DNDEBUG -D_CRT_SECURE_NO_WARNINGS -<br>I"/var/boost/run/boost_root" -c -o "../../bin/common/build/gcc-8/release/process_jam_log.o" "../../common/build/../src/p<br>rocess_jam_log.cpp"
<br>
<br>../../common/build/../src/process_jam_log.cpp: In function 'std::__cxx11::string {anonymous}::revision(const string&)':
<br>../../common/build/../src/process_jam_log.cpp:359:16: warning: ignoring return value of 'int system(const char*)', decla<br>red with attribute warn_unused_result [-Wunused-result]
<br> std::system("git rev-parse --short=6 HEAD >.short-sha");
<br> ~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<br>...skipped <p../../bin/testing/build/gcc-8/release>process_jam_log for lack of <p/var/boost/run/boost_root/bin.v2/libs/f<br>ilesystem/build/gcc-8/release/link-static/visibility-hidden>libboost_filesystem.a...
<br></span></div></div></blockquote><div><br></div><div>I guess you'd need to find out what it says for trying to build filesystem lib.</div></div></div></blockquote><div><br></div><div> Here's what I'm seeing with the filesystem error:</div><div><br></div><div><div><span style="font-family:monospace"> ln -f -s "../../libs/detail/include/boost/detail/has_default_constructor.hpp" "../../../boost_root/boost/detail/has_ <br>default_constructor.hpp" <br><br>gcc.compile.c++ /var/boost/run/boost_root/bin.v2/libs/filesystem/build/gcc-8/release/link-static/visibility-hidden/path_traits.o <br><br> "g++-8" -fvisibility-inlines-hidden -m64 -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden -DBOOST_ALL <br>_NO_LIB=1 -DBOOST_FILESYSTEM_STATIC_LINK=1 -DNDEBUG -I"/var/boost/run/boost_root" -c -o "/var/boost/run/boost_root/bin. <br>v2/libs/filesystem/build/gcc-8/release/link-static/visibility-hidden/path_traits.o" "/var/boost/run/boost_root/libs/file <br>system/src/path_traits.cpp" <br><br>/var/boost/run/boost_root/libs/filesystem/src/path_traits.cpp:20:10: fatal error: boost/filesystem/config.hpp: No such f <br>ile or directory <br>#include <boost/filesystem/config.hpp> <br> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ <br>compilation terminated. <br>...failed gcc.compile.c++ /var/boost/run/boost_root/bin.v2/libs/filesystem/build/gcc-8/release/link-static/visibility-hidden/path_traits.o... <br>gcc.compile.c++ /var/boost/run/boost_root/bin.v2/libs/filesystem/build/gcc-8/release/link-static/visibility-hidden/portability.o <br><br> "g++-8" -fvisibility-inlines-hidden -m64 -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden -DBOOST_ALL<br>_NO_LIB=1 -DBOOST_FILESYSTEM_STATIC_LINK=1 -DNDEBUG -I"/var/boost/run/boost_root" -c -o "/var/boost/run/boost_root/bin.<br>v2/libs/filesystem/build/gcc-8/release/link-static/visibility-hidden/portability.o" "/var/boost/run/boost_root/libs/file<br>system/src/portability.cpp" <br><br>/var/boost/run/boost_root/libs/filesystem/src/portability.cpp:20:10: fatal error: boost/filesystem/config.hpp: No such f<br>ile or directory <br>#include <boost/filesystem/config.hpp> <br> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ <br>compilation terminated. <br>...failed gcc.compile.c++ /var/boost/run/boost_root/bin.v2/libs/filesystem/build/gcc-8/release/link-static/visibility-hidden/portability.o... </span></div><div><span style="font-family:monospace"><br></span></div><div><br></div></div><div>And several more like that.</div><div><br></div><div>However, I'm also suspicious of the timing with the processor change.</div><div><br></div><div>Looking back at the last successful builds of develop on linux. I have a few from linux/x86_64/docker machines. The last one I saw was building with gcc-8 on June 4 around 6:30am CDT. There should have been a successful clang run about 5hrs after that (11:30am CDT), and another successful gcc around 10hrs after the last one that was actually successful (4:30pm CDT). </div><div><br></div><div>This seems like it would correspond to the change to build here:<br><a href="https://github.com/boostorg/build/commit/451059949d92b52b21f802562a50587f1eeecb82">https://github.com/boostorg/build/commit/451059949d92b52b21f802562a50587f1eeecb82</a><br></div><div><br></div><div>The other failure I started seeing was only my linux/arm64 machine. This doesn't run docker, so might not be affected in the same way. The last successful run on there was at 4:50pm CDT on June 4...but it typically takes around 9hrs to run so it probably got the pre 451059949 commit. However here I can't rule out that it was impacted by a8ab76ef973.</div><div><br></div><div>I'm going to try to standup some normal VMs soon and run on them to see if they are affected in the same way. It would also be nice if we could try backing out the usage of _SC_NPROCESSORS_ONLN and see if that fixes things, is that feasible to try for a couple days?</div><div><br></div><div>Thanks,</div><div>Tom</div><div><br></div><div><br></div></div></div></div>