Hello. Can't build openoffice right now, noticed during last libxml bump. ... Checking DLL ../../unxfbsdx.pro/lib/check_cppobj.uno.so ...-rwxr-xr-x 1 root wheel 302144 Apr 15 17:34 ../../unxfbsdx.pro/lib/cppobj.uno.so Checking DLL ../../unxfbsdx.pro/lib/check_bridgetest.uno.so ...-rwxr-xr-x 1 root wheel 203096 Apr 15 17:34 ../../unxfbsdx.pro/lib/bridgetest.uno.so cd ../../unxfbsdx.pro/lib && : && LD_LIBRARY_PATH=/tmp/ports/usr/ports/editors/openoffice-4/work/aoo-4.1.11/main/solver/4111/unxfbsdx.pro/lib${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}} /tmp/ports/usr/ports/editors/openoffice-4/work/aoo-4.1.11/main/solver/4111/unxfbsdx.pro/bin/uno \ -ro uno_services.rdb -ro uno_types.rdb \ -s com.sun.star.test.bridge.BridgeTest -- \ com.sun.star.test.bridge.CppTestObject dmake: Error code 138, while making 'runtest' ... 1 module(s): testtools need(s) to be rebuilt Reason(s): ERROR: error 65280 occurred while making /tmp/ports/usr/ports/editors/openoffice-4/work/aoo-4.1.11/main/testtools/source/bridgetest ... This is build on real host, amd64, 13.1-STABLE, from a few says ago. No compilation errors in logs, just some warnings. Thank in advance.
I suspect this a failing low-level unit test. The output from these tests should look something like: [----------] 8 tests from BigPtrArrayPerformanceTest [ RUN ] BigPtrArrayPerformanceTest.test_insert_at_end_1000 [ OK ] BigPtrArrayPerformanceTest.test_insert_at_end_1000 (0 ms) [ RUN ] BigPtrArrayPerformanceTest.test_insert_at_end_10000 [ OK ] BigPtrArrayPerformanceTest.test_insert_at_end_10000 (2 ms) [ RUN ] BigPtrArrayPerformanceTest.test_insert_at_end_100000 [ OK ] BigPtrArrayPerformanceTest.test_insert_at_end_100000 (21 ms) [ RUN ] BigPtrArrayPerformanceTest.test_insert_at_end_1000000 [ OK ] BigPtrArrayPerformanceTest.test_insert_at_end_1000000 (213 ms) [ RUN ] BigPtrArrayPerformanceTest.test_insert_at_front_1000 [ OK ] BigPtrArrayPerformanceTest.test_insert_at_front_1000 (1 ms) [ RUN ] BigPtrArrayPerformanceTest.test_insert_at_front_10000 [ OK ] BigPtrArrayPerformanceTest.test_insert_at_front_10000 (13 ms) [ RUN ] BigPtrArrayPerformanceTest.test_insert_at_front_100000 [ OK ] BigPtrArrayPerformanceTest.test_insert_at_front_100000 (319 ms) [ RUN ] BigPtrArrayPerformanceTest.test_insert_at_front_1000000 but if there is a failure, you will see FAIL instead of OK as I recall. A few years ago I fixed several of these upstream that had intermittent timing failures that would sometimes show up if the build system was heavily loaded. I haven't seen a failure in quiet some time.
Nothing usable in the log sample and no feedback from OP