public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: ",Erwin Waterlander" <waterlan@xs4all.nl>,
	"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: some libunistring 1.0 tests are core dumping on github build
Date: Sun, 30 Oct 2022 13:15:31 +0000	[thread overview]
Message-ID: <f1734b4e-7b82-4939-ac56-8e7f880b6048@dronecode.org.uk> (raw)
In-Reply-To: <738273773.183961.1666191343231@kpc.webmail.kpnmail.nl>

On 19/10/2022 15:55, Erwin Waterlander wrote:
> Hi,
>   
> I uploaded a new cyport file for libunistring 1.0. I got a failed build, because several tests core dumped. This does not happen when I run the tests on my PC. What to do next?
>   
> See https://github.com/cygwin/scallywag/actions/runs/3252280207

Interesting.

The builddir artefact should contain the entire build directory, 
including any .stackdump files generated, which might give some insight.



  reply	other threads:[~2022-10-30 13:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 14:55 Erwin Waterlander
2022-10-30 13:15 ` Jon Turney [this message]
2022-10-30 15:56 Brian Inglis

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=f1734b4e-7b82-4939-ac56-8e7f880b6048@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@cygwin.com \
    --cc=waterlan@xs4all.nl \
    /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).