Am 25.02.2019 um 12:10 schrieb Kornel Benko <kor...@lyx.org>: > > Am Montag, 25. Februar 2019 11:36:41 CET schrieb Stephan Witt > <st.w...@gmx.net>: >> Am 25.02.2019 um 10:31 schrieb Kornel Benko <kor...@lyx.org>: >>> >>> Am Montag, 25. Februar 2019 10:09:40 CET schrieb Stephan Witt >>> <st.w...@gmx.net>: >>>> Am 25.02.2019 um 09:20 schrieb Kornel Benko <kor...@lyx.org>: >>>>> >>>>> Am Montag, 25. Februar 2019 07:17:29 CET schrieb Stephan Witt >>>>> <st.w...@gmx.net>: >>>>>> Am 24.02.2019 um 21:43 schrieb Kornel Benko <kor...@lyx.org>: >>>>>>> >>>>>>> Am Sonntag, 24. Februar 2019 19:23:25 CET schrieb Stephan Witt >>>>>>> <st.w...@gmx.net>: >>>>>>>> >>>>>>>> >>>>>>>> I’m able to run the tests with auto tools. The target RUN_TESTS of the >>>>>>>> cmake >>>>>>>> project fails to run the executables. I don’t know how to solve that. >>>>>>> >>>>>>> Hm, I never use this target. >>>>>>> What happens if you run >>>>>>> $ ctest -N >>>>>>> from inside the build directory? >>>>>>> (It should list all the possible tests, without actually execute them) >>>>>> >>>>>> No tests are made or listed. >>>>>> >>>>>> ================== >>>>>> $ (cd lyx-build/LyX-2.3.3dev.build;ctest -N) >>>>>> Test project /Users/stephan/git/lyx-build/LyX-2.3.3dev.build >>>>>> >>>>>> Total Tests: 0 >>>>>> ================== >>>>>> >>>>>> ctest --debug says it’s looking for CTestCustom.cmake, CTestCustom.ctest >>>>>> and >>>>>> for DartConfiguration.tcl but there isn’t such a file - >>>>>> neither in source tree nor in build tree. >>>>>> >>>>>> ================== >>>>>> cmCTest.cxx:380 Here: 380 >>>>>> cmCTest.cxx:687 UpdateCTestConfiguration from >>>>>> :/Users/stephan/git/lyx-build/LyX-2.3.3dev.build/DartConfiguration.tcl >>>>>> cmCTest.cxx:392 Here: 392 >>>>>> cmCTest.cxx:2385 * Read custom CTest configuration directory: >>>>>> /Users/stephan/git/lyx-build/LyX-2.3.3dev.build >>>>>> cmCTest.cxx:2389 * Check for file: >>>>>> /Users/stephan/git/lyx-build/LyX-2.3.3dev.build/CTestCustom.cmake >>>>>> cmCTest.cxx:2411 * Check for file: >>>>>> /Users/stephan/git/lyx-build/LyX-2.3.3dev.build/CTestCustom.ctest >>>>>> cmCTest.cxx:687 UpdateCTestConfiguration from >>>>>> :/Users/stephan/git/lyx-build/LyX-2.3.3dev.build/DartConfiguration.tcl >>>>>> CTest/cmCTestTestHandler.cxx:480 Test project >>>>>> /Users/stephan/git/lyx-build/LyX-2.3.3dev.build >>>>>> CTest/cmCTestTestHandler.cxx:1657 Constructing a list of tests >>>>>> CTest/cmCTestTestHandler.cxx:871 Updating test list for fixtures >>>>>> CTest/cmCTestTestHandler.cxx:1104 Added 0 tests to meet fixture >>>>>> requirements >>>>>> cmCTest.cxx:146 Current_Time: Feb 25 07:13 CET >>>>>> cmCTest.cxx:146 Current_Time: Feb 25 07:13 CET >>>>>> CTest/cmCTestMultiProcessHandler.cxx:754 >>>>>> Total Tests: 0 >>>>>> cmCTest.cxx:146 Current_Time: Feb 25 07:13 CET >>>>>> cmCTest.cxx:146 Current_Time: Feb 25 07:13 CET >>>>>> ================== >>>>>> >>>>>> Stephan >>>>>> >>>>>> >>>>> >>>>> OK, so you have probably configured without enabling any tests. >>>>> To enable export tests you have to add >>>>> -DLYX_ENABLE_EXPORT_TESTS=ON >>>>> to cmake's command line. >>>> >>>> Yes, that’s the case. I did it but it doesn’t change anything for the >>>> ctest call. >>>> But it adds this to the cmake call: >>>> -- Found Perl: /opt/local/bin/perl (found version "5.26.2") >>>> -- Reading list invertedTests >>>> -- Reading list ignoredTests >>>> -- Reading list suspendedTests >>>> -- Reading list unreliableTests >>>> -- Reading list ignoreLatexErrorsTests >>>> -- Handling export dir /Users/stephan/git/lyx-2.3.x/autotests/export >>>> -- Handling export dir /Users/stephan/git/lyx-2.3.x/lib/doc >>>> -- Handling export dir /Users/stephan/git/lyx-2.3.x/lib/examples >>>> -- Handling export dir /Users/stephan/git/lyx-2.3.x/lib/templates >>>> -- Handling export dir /Users/stephan/git/lyx-2.3.x/autotests/mathmacros >>>> >>>> I’m able to run these tests (IMO) with the cmake target lyx_run_tests: >>>> $ xcodebuild -project lyx-build/cmake/2.3.3dev/LyX.xcodeproj -target >>>> lyx_run_tests >>>> >>>> This is a long running task with more than 6000 steps - most of them >>>> failing. >>>> The output looks like this: >>>> Start 4598: export/examples/de/serienbrief3_lyx16 >>>> 4598/6656 Test #4598: export/examples/de/serienbrief3_lyx16 >>>> ................................................................................................***Failed >>>> 0.14 sec >>>> Start 4599: export/examples/de/serienbrief3_lyx21 >>>> 4599/6656 Test #4599: export/examples/de/serienbrief3_lyx21 >>>> ................................................................................................***Failed >>>> 0.14 sec >>>> Start 4600: export/examples/de/serienbrief3_lyx22 >>>> 4600/6656 Test #4600: export/examples/de/serienbrief3_lyx22 >>>> ................................................................................................***Failed >>>> 0.14 sec >>>> Start 4601: lyx2lyx/examples/de/serienbrief3 >>>> 4601/6656 Test #4601: lyx2lyx/examples/de/serienbrief3 >>>> ..................................................................................................... >>>> Passed 0.17 sec >>>> Start 4602: check_load/examples/de/serienbrief3 >>>> 4602/6656 Test #4602: check_load/examples/de/serienbrief3 >>>> .................................................................................................. >>>> Passed 0.29 sec >>>> Start 4603: export/examples/de/serienbrief3_xhtml >>>> 4603/6656 Test #4603: export/examples/de/serienbrief3_xhtml >>>> ................................................................................................***Failed >>>> 0.14 sec >>>> Start 4604: export/examples/de/serienbrief3_dvi >>>> 4604/6656 Test #4604: export/examples/de/serienbrief3_dvi >>>> ..................................................................................................***Failed >>>> 0.14 sec >>>> Start 4605: export/examples/de/serienbrief3_dvi3_texF >>>> 4605/6656 Test #4605: export/examples/de/serienbrief3_dvi3_texF >>>> ............................................................................................***Failed >>>> 0.15 sec >>>> >>>> Do you know where I can look for log files to see what went wrong with the >>>> failed tests? >>>> >>>> Stephan >>>> >>> >>> Yes. But the log is very lengthy. >>> The primary log-file is in the build-dir under >>> Testing/Temporary/LastTest.log >>> >>> But I suggest you prepare yourself to use 'ctest' directly. >>> Step 1: prepare tests for lyx to use external programs (needed only the >>> firs time) >>> $ cd build-dir >>> $ perl ./prefTest.pl test >>> Step 2: check only a subgroup of tests (using 8 cores) >>> $ ctest -R '_texF$' -j8 >>> Step 3: Retest only 1 failed test >>> $ ctest -R 'export/examples/de/serienbrief3_dvi' >>> Step 4: check the logfile >>> $ edit Testing/Temporary/LastTest.log >>> >>> In case you need the latex output: >>> Step 3a: (in csh syntax, else use 'export') >>> $ setenv LYX_DEBUG_LATEX 1 >>> $ ctest -R 'export/examples/de/serienbrief3_dvi‘ >> >> Ok, thank you. When using the right build directory I’m able to use ctest >> too ;-) >> >> Now there seems to be a fundamental problem here: all tests complaining… >> "Test not available without configuration. (Missing "-C <config>“?)" >> >> What config? > > I never have seen this. '-C' is used to pre-load the cache, but > in the _right_ directory there should be a file CMakeCache.txt > with all cached data already.
This file is there. If you think it’s useful I’ll send it to you. In debug mode I can see a line before the mentioned one with: 4606: Test command: NOT_AVAILABLE Is it the lyx binary? Perhaps it’s at an unusual place. Stephan
