See below what I said in both January and November the last times we had any
conversation on this. cmake_minimum_required, project_injected, and CommandLine
test failures are new and I'd personally come to a definitive thoroughly
researched conclusion on what's causing them before making a release. But I
don't intend on making any releases of cygwin packages any time soon, so you
can do whatever you want here.
---- top-posting because these conversations were off list:
Right, if the logs aren't super useful for debugging, then the next step I'd do
is what I said in November:
> What happens if you run the steps those tests are trying to execute on their
> own, not under ctest? Or try to run the unit tests with an existing older
> separate copy of ctest instead of the just-built copy?
The Qt*Autogen failures were pre-existing and I've identified the cause in past
versions, I should have made a note of it in writing somewhere more permanent
though. The build system there isn't handling dll dependencies of the test
executables quite correctly for cygwin. That's definitely a bug in how the test
is written and could eventually be resolved with a cygwin-specific patch to
those cmake tests by whoever ever has the time to work through it. The new ones
are what I was referring to and could be indicative of real problems. It's
possible some of them are due to missing dll issues like the Qt*Autogen
failures but that would surprise me a little. Running the executables manually
or outside of cygwin/ctest can sometimes give more useful output on problems
like that (from windows popups, etc).
From: Marco Atzeri <marco.atz...@gmail.com>
Sent: Thursday, January 10, 2019 5:49 AM
To: Tony Kelman; Ivan Shynkarenka
Subject: Re: refreshing cmake
Am 1/9/2019 um 7:28 AM schrieb Tony Kelman:
> I still think the test failures should be looked into and debugged,
> personally.
Tony,
to me it seems a case of best is enemy of good.
I look at the test log and I do not see what is the problem
so I am not able to debug.
Do you have some guidance ?
-------------------------------------
Start 359: RunCMake.cmake_minimum_required
359/561 Test #359: RunCMake.cmake_minimum_required
..................***Failed
$ find . -name CMakeOutput.log -exec cat {} \;
The system is: CYGWIN - 2.11.2(0.329/5/3) - x86_64
The system is: CYGWIN - 2.11.2(0.329/5/3) - x86_64
The system is: CYGWIN - 2.11.2(0.329/5/3) - x86_64
The system is: CYGWIN - 2.11.2(0.329/5/3) - x86_64
The system is: CYGWIN - 2.11.2(0.329/5/3) - x86_64
The system is: CYGWIN - 2.11.2(0.329/5/3) - x86_64
The system is: CYGWIN - 2.11.2(0.329/5/3) - x86_64
there is nothing more.
-----------------------------------------------
Start 391: RunCMake.project_injected
391/561 Test #391: RunCMake.project_injected
........................***Failed
the single log is very long but I do not see a single error.
------------------------------------------------
Start 422: RunCMake.CommandLine
422/561 Test #422: RunCMake.CommandLine
.............................***Failed
the single log is very long but I do not see a single error.
------------------------------------------------
Start 454: Qt5Autogen.Complex
454/561 Test #454: Qt5Autogen.Complex
...............................***Failed
the single log shows no error.
There is just an isolated warning
all the targets seem built
$ find . -name "*.a" -or -name "*.dll" -or -name "*.exe"
./Adir/cyglibA.dll
./Adir/liblibA.dll.a
./Bdir/cyglibB.dll
./Bdir/liblibB.dll.a
./CMakeFiles/3.13.1/CompilerIdC/a.exe
./CMakeFiles/3.13.1/CompilerIdCXX/a.exe
./cyglibC.dll
./libcodeeditorLib.a
./liblibC.dll.a
./QtAutogen.exe
./targetObjectsTest.exe
$ PATH=$(PWD)/Adir:$(PWD)/Bdir:$PATH ./QtAutogen
Hello automoc: 12
Blub blub 13 !
Hello bar !
abc
I am private abc !
This is xyz !
I am yet another file !
just ./targetObjectsTest.exe produces no output at all
so I have no clue of what is supposed to do.
----------------------------------------------
Start 487: Qt4Autogen.Complex
487/561 Test #487: Qt4Autogen.Complex
...............................***Failed
same a QT5
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
