From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: CI system cryptic error
Date: Fri, 21 Jan 2022 16:03:39 +0000 [thread overview]
Message-ID: <DB3PR0202MB35617233F484BAD209A18ADCE75B9@DB3PR0202MB3561.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <fa12f88f-0d24-50c4-ad19-f308473edcaf@dronecode.org.uk>
On 21/01/2022 14:06, Jon Turney wrote:
> On 20/01/2022 15:50, Hamish McIntyre-Bhatty wrote:
>> Hi there,
>>
>> Recently, I created a test package for python-imaging, and the CI
>> system gave a build error that I didn't see locally:
>>
>> *** ERROR: unknown wheel filename.
>>
>> This only occurred for the Python 3.8 build (3.6 and 3.7 are
>> unaffected). Considering some of the library name changes between
>> these versions, is it possible that this is a bug in the CI tool setup
>> or in cygport?
>
> Weird.
>
> I assume it's this job:
> https://github.com/cygwin/scallywag/actions/runs/1592256829
Yep, sorry I forgot to add the link.
>
> In which case further note it only failed with this error on i686,
> x86_64 seems to have built ok. That might explain why you don't see it
> locally, at least, but it's still puzzling that there's a difference.
No I did a local i686 build too, and it was fine...
>
> This error comes from here:
>
> https://cygwin.com/git/?p=cygwin-apps/cygport.git;a=blob;f=cygclass/python-wheel.cygclass;h=90b0faac71eea6005401b4232e5b334bdc81b756;hb=HEAD#l190
>
>
> and means something more like "couldn't find the wheel file for python
> $ver"
>
> I downloaded the builddir archive, and inspecting that it seems that a
> wheel for python3.8 (and 3.9!) isn't being generated.
>
>> $ tar -tf builddir.tar.xz | grep whl
>> python-imaging-8.4.0-1.i686/build/dist/Pillow-8.4.0-cp36-cp36m-cygwin_3_3_3_i686.whl
>>
>> python-imaging-8.4.0-1.i686/build/dist/Pillow-8.4.0-cp37-cp37m-cygwin_3_3_3_i686.whl
>>
>
> There seems to be completely different output between x86_64 and i686
> when building the python wheel, but I have no idea why!
>
Hmm, very strange. Maybe just a freak error? I'll try building again,
seeing as I have a new version now anyway, and see what happens. I guess
seeing as 64-bit builds are the future for Cygwin, I'll just ignore this
issue if it happens again, as long as I check the 32-bit builds I built
work.
Hamish
next prev parent reply other threads:[~2022-01-21 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 15:50 Hamish McIntyre-Bhatty
2022-01-21 14:06 ` Jon Turney
2022-01-21 16:03 ` Hamish McIntyre-Bhatty [this message]
2022-01-22 5:34 ` Marco Atzeri
2022-01-22 12:11 ` Hamish McIntyre-Bhatty
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=DB3PR0202MB35617233F484BAD209A18ADCE75B9@DB3PR0202MB3561.eurprd02.prod.outlook.com \
--to=hamishmb@live.co.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).