public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH] Cygwin: Run testsuite against the just-built DLL
Date: Mon, 9 Jan 2023 12:12:52 +0100	[thread overview]
Message-ID: <Y7v2tBwkd79plnBd@calimero.vinschen.de> (raw)
In-Reply-To: <20230106143823.53627-1-jon.turney@dronecode.org.uk>

On Jan  6 14:38, Jon Turney wrote:
> Since 4e7817498efc, we're just running the tests against the installed
> DLL.  We're arranging to put the build directory on the path, but since
> it doesn't contain cygwin1.dll (since it's built with a different name
> and renamed on installation), that doesn't have any effect.
> 
> Arrange to place the just-built DLL into a directory which the testsuite
> can place on it's path (while running the test, but not while compiling
> it).
> 
> Also fix any remaining references to cygwin0.dll in testsuite,
> documentation and comments.
> 
> Fixes: 4e7817498efc ("Cygwin: Makefile: Drop all the "test dll" considerations")
> ---
> 
> Notes:
>     This flips a couple of tests from passing to failing, since they try to
>     use system(), which doesn't work, because there is no /usr/bin/bash in
>     the Cygwin 'installation' at testsuite/runtime/.
>     
>     I think perhaps the best solution long-term is to remove all these
>     fragile hacks to try to run the testsuite on top of an existing Cygwin,
>     and instead the CI should save the result of 'make install' in an
>     archive, and a job should unpack that and run the testsuite on it...
> 
>  winsup/cygwin/Makefile.am               | 8 +++++---
>  winsup/cygwin/scripts/analyze_sigfe     | 2 +-
>  winsup/testsuite/Makefile.am            | 3 ++-
>  winsup/testsuite/README                 | 9 +++------
>  winsup/testsuite/config/default.exp     | 2 +-
>  winsup/testsuite/winsup.api/cygload.exp | 2 +-
>  winsup/testsuite/winsup.api/winsup.exp  | 8 +++++---
>  7 files changed, 18 insertions(+), 16 deletions(-)

All your patches to the testsuite are auto-approved.

Just go ahead with whatever you deem right.  We can handle any question
on IRC.


Thanks,
Corinna

      reply	other threads:[~2023-01-09 11:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-21 13:49 [PATCH] Cygwin: Makefile: Build new DLL with the name 'cygwin0.dll' Jon Turney
2022-12-21 15:58 ` [PATCH] Cygwin: Makefile: Also make 'cygwin0.dll' Jon Turney
2022-12-21 16:18 ` [PATCH] Cygwin: Makefile: Drop all the "test dll" considerations Jon Turney
2023-01-06 14:38   ` [PATCH] Cygwin: Run testsuite against the just-built DLL Jon Turney
2023-01-09 11:12     ` Corinna Vinschen [this message]

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=Y7v2tBwkd79plnBd@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin-patches@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).