public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Tony Kelman <tony@kelman.net>
To: Marco Atzeri <marco.atzeri@gmail.com>,
	"cygwin@cygwin.com"	<cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Test: cmake-3.13.1-1
Date: Tue, 04 Jun 2019 23:22:00 -0000	[thread overview]
Message-ID: <CY4PR22MB07731E5A2654E198D7711CC3A7150@CY4PR22MB0773.namprd22.prod.outlook.com> (raw)
In-Reply-To: <343610ae-e076-c0ee-ef6d-fa4f9aa4eb88@gmail.com>

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.atzeri@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

  reply	other threads:[~2019-06-04 23:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-29  9:27 Marco Atzeri
2019-05-28  2:39 ` Steven Penny
2019-05-30  8:11   ` Marco Atzeri
2019-05-30 16:05     ` Yaakov Selkowitz
2019-06-04  7:42       ` Marco Atzeri
2019-06-04 23:22         ` Tony Kelman [this message]
2019-06-05  9:07           ` Marco Atzeri
2019-05-30 10:31 Ivan Shynkarenka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CY4PR22MB07731E5A2654E198D7711CC3A7150@CY4PR22MB0773.namprd22.prod.outlook.com \
    --to=tony@kelman.net \
    --cc=cygwin@cygwin.com \
    --cc=marco.atzeri@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).