public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Test: cmake-3.13.1-1
Date: Thu, 30 May 2019 08:11:00 -0000	[thread overview]
Message-ID: <9cee1fa8-2a10-4d4f-9745-8b13a1dac911@gmail.com> (raw)
In-Reply-To: <5cec9f58.1c69fb81.6f378.05ce@mx.google.com>

Am 28.05.2019 um 04:39 schrieb Steven Penny:
> On Thu, 29 Nov 2018 07:58:53, Marco Atzeri wrote:
>> Test version 3.13.3-1 of
>>
>>    cmake
>>    cmake-doc
>>    cmake-gui
>>    emacs-cmake
>>
>> are available in the Cygwin distribution.
>>
>> Please test and report here any issue or problem.
>> Also positive feedback in complex projects are appreciated
>>
>> CHANGES
>> Last upstream  release.
> 
> https://cygwin.com/ml/cygwin/2018-11/msg00234.html
> 
> Can we please move this out of test?
> 


I have no problem, but Tony thinks that as the cmake test suite test
is not perfect so he prefers to stay with the old one.

99% tests passed, 4 tests failed out of 548


I was not able to identify the failures root cause,
and I suspect they are not fundamental and related to the test
suite itfelf.

Regards
Marco








---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


--
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-05-30  8:11 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 [this message]
2019-05-30 16:05     ` Yaakov Selkowitz
2019-06-04  7:42       ` Marco Atzeri
2019-06-04 23:22         ` Tony Kelman
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=9cee1fa8-2a10-4d4f-9745-8b13a1dac911@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.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).