unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ken Brown <kbrown@cornell.edu>
Cc: 62420@debbugs.gnu.org
Subject: bug#62420: 29.0.60; fns-tests-collate-strings fails on Cygwin
Date: Sat, 25 Mar 2023 17:46:55 +0300	[thread overview]
Message-ID: <83tty8c2hs.fsf@gnu.org> (raw)
In-Reply-To: <4ebca72d-39f4-afa3-9eca-e45442f8640a@cornell.edu> (message from Ken Brown on Sat, 25 Mar 2023 10:27:51 -0400)

> Date: Sat, 25 Mar 2023 10:27:51 -0400
> Cc: 62420-done@debbugs.gnu.org
> From: Ken Brown <kbrown@cornell.edu>
> 
> On 3/25/2023 8:24 AM, Eli Zaretskii wrote:
> >> Date: Fri, 24 Mar 2023 10:52:45 -0400
> >> From: Ken Brown <kbrown@cornell.edu>
> >> Is this OK for the emacs-29 branch?
> > 
> > Yes, thanks.
> > 
> >> [Note: The test will still fail on current Cygwin after this patch; but
> >> that's because of a bug in Cygwin, which has been fixed in the
> >> development sources for Cygwin 3.5.]
> > 
> > Maybe mention this in comments?
> 
> Done.

Thanks.

> >  Bonus points for making it an
> > expected failure for Cygwin < 3.5, assuming the version of Cygwin
> > could be obtained by the test code.
> 
> I don't know how to get the version in Lisp.  I only know how to get it 
> in C, using uname.  If someone can tell me how to get it in Lisp, I'll 
> try to earn the bonus points.

What's the value of operating-system-release return in a Cygwin build?





  reply	other threads:[~2023-03-25 14:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24 14:52 bug#62420: 29.0.60; fns-tests-collate-strings fails on Cygwin Ken Brown
2023-03-25 12:24 ` Eli Zaretskii
2023-03-25 14:27   ` Ken Brown
2023-03-25 14:46     ` Eli Zaretskii [this message]
2023-03-25 15:02       ` Corwin Brust
2023-03-25 15:14       ` Ken Brown
2023-03-25 15:49         ` Eli Zaretskii
2023-03-25 16:47           ` Ken Brown

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=83tty8c2hs.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=62420@debbugs.gnu.org \
    --cc=kbrown@cornell.edu \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).