public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: g-ir-scanner fails with python-3.8
Date: Sun, 23 May 2021 19:13:52 +0100	[thread overview]
Message-ID: <c1d37437-ef7c-12bb-4f6b-b727008451b5@dronecode.org.uk> (raw)
In-Reply-To: <20210523084421.9873.50F79699@gmail.com>

On 23/05/2021 00:44, Lemures Lemniscati via Cygwin-apps wrote:
> 
> And with them, following build and test by cygport has succeeded
> both in x86_64 and i686, on my local machine.
> 
>    cygport gobject-introspection.cygport download finish all test
> 
> 
> But on scallywag, only x86_64 build is successful:
> https://cygwin.com/cgi-bin2/jobs.cgi?id=2841

Yeah, I don't know why the x86 build fails in the AppVeyor environment.

Downloading the builddir artifact, there isn't even a stackdump file, so 
the only way I can think of investigating futher is to RDP into the 
AppVeyor VM and try to trigger the crash with 'CYGWIN=error_start:gdb' set.

  parent reply	other threads:[~2021-05-23 18:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19 19:32 Ken Brown
2021-05-19 21:09 ` Jon Turney
2021-05-22 23:44   ` Lemures Lemniscati
2021-05-23  3:51     ` Marco Atzeri
2021-05-23  4:01       ` Marco Atzeri
2021-05-23  4:45         ` Marco Atzeri
2021-05-23  5:04         ` Lemures Lemniscati
2023-01-12 19:50           ` Jon Turney
2021-05-23  6:00     ` Brian Inglis
2021-05-23 11:50       ` Lemures Lemniscati
2021-05-23 18:17         ` Jon Turney
2021-05-23 18:13     ` Jon Turney [this message]
2021-05-19 21:21 ` 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=c1d37437-ef7c-12bb-4f6b-b727008451b5@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@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).