From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: Testing is skipped on i686-AppVeyor for shared-mime-info 2.1
Date: Wed, 6 Jan 2021 15:02:31 +0000 [thread overview]
Message-ID: <377188eb-416b-83b5-0a12-1742374d1cd1@dronecode.org.uk> (raw)
In-Reply-To: <20210104234114.24EC.50F79699@gmail.com>
On 04/01/2021 14:41, Lemures Lemniscati via Cygwin-apps wrote:
> Hi!
>
> I'm preparing share-mime-info-2.1-1, updating to the latest upstream.
>
> My local-buildings run and check successfull both on i686 and x86_64
> with a source tree [1].
>
> But on AppVeyor [2], testing seems to be skipped on i686 arch, although
> src_test is called [3]... On the other hand, testing is successful on
> x86_64 arch [4].
>
>
> I don't know the reason of this behavior.
> Is there any similar case or advice?
That's pretty odd.
I can only guess that perhaps a prerequsite for the test isn't present
during the i686 build?
prev parent reply other threads:[~2021-01-06 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 14:41 Lemures Lemniscati
2021-01-06 15:02 ` Jon Turney [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=377188eb-416b-83b5-0a12-1742374d1cd1@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).