public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ivan Shynkarenka <chronoxor@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Test: cmake-3.13.1-1
Date: Thu, 30 May 2019 10:31:00 -0000	[thread overview]
Message-ID: <CAHVoUt0KCKGS8frgnYdhaiBaJ52KrfYGX8UageUxk52T_Q44kw@mail.gmail.com> (raw)

>
> 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
>
>
Old cmake 3.6.2-1 is very-very old and not actual in C++ world. I use new
cmake 3.13.1-1 test version for half a year and see no issues. I think 4
failed tests of 548 that are not affect of main functionality is not a good
reason to delay cmake release for so long time...

I vote to move a new cmake from test to release!

--
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 10:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30 10:31 Ivan Shynkarenka [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
2019-06-05  9:07           ` Marco Atzeri

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=CAHVoUt0KCKGS8frgnYdhaiBaJ52KrfYGX8UageUxk52T_Q44kw@mail.gmail.com \
    --to=chronoxor@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).