CI system cryptic error

CI system cryptic error

[Hamish McIntyre-Bhatty]

[-- Attachment #1: Type: text/plain, Size: 455 bytes --]

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?

Attached is the offending cygport file that caused the error.

Hamish

[-- Attachment #2: python-imaging.cygport --]
[-- Type: text/plain, Size: 4442 bytes --]

ORIG_PN="Pillow"
PYTHON_WHEEL_VERSIONS="3.6:3.7:3.8:3.9"
inherit python-wheel

NAME="python-imaging"
VERSION=8.4.0
RELEASE=1
CATEGORY="Python"
SUMMARY="Python Imaging Library"
DESCRIPTION="The Python Imaging Library (PIL) adds image processing capabilities
to your Python interpreter. This library supports many file formats, and provides
powerful image processing and graphics capabilities."
HOMEPAGE="https://python-pillow.github.io/"

SRC_URI="https://files.pythonhosted.org/packages/7d/2a/2fc11b54e2742db06297f7fa7f420a0e3069fdcf0e4b57dfec33f0b08622/Pillow-8.4.0.tar.gz"
SRC_DIR="Pillow-${VERSION}"
PATCH_URI=""

BUILD_REQUIRES="libjpeg-devel libjpeg8 zlib-devel zlib0 libtiff-devel libtiff6 libfreetype-devel libfreetype6 liblcms2-devel lcms2 libwebp libwebp-devel tcl-devel tcl libimagequant-devel libimagequant0 libraqm-devel libraqm0 libX11-xcb-devel libX11-xcb1 libxcb-devel libxcb1 python36 python36-devel python36-setuptools python36-wheel python36-pip python36-olefile python37 python37-devel python37-setuptools python37-wheel python37-pip python37-olefile python38 python38-devel python38-setuptools python38-wheel python38-pip python38-olefile python39 python39-devel python39-setuptools python39-wheel python39-pip python39-olefile"

DIFF_EXCLUDES="build"

src_test() {
	cd ${B}
	for v in ${PYTHON_WHEEL_VERSIONS//:/ }
	do
		echo PYTHONPATH="${B}/build/lib.cygwin-$(uname -r | sed -e 's|s*(.*||')-$(uname -m)-$v"
		PYTHONPATH="${B}/build/lib.cygwin-$(uname -r | sed -e 's|s*(.*||')-$(uname -m)-$v" \
		python$v selftest.py
	done
}

PKG_NAMES=" python36-imaging python36-imaging-tk"
PKG_NAMES+=" python37-imaging python37-imaging-tk"
PKG_NAMES+=" python38-imaging python38-imaging-tk"
PKG_NAMES+=" python39-imaging python39-imaging-tk"

# ImageQt no longer imports PyQt or PySide, but simply integrates with
# whatever has already been imported.  Therefore there is no need to
# break it out separately, as it has no hard dependencies of its own.
python36_imaging_REQUIRES="python36 python36-olefile"
python36_imaging_OBSOLETES+=" python3-imaging-devel python3-imaging-qt"
python36_imaging_CONTENTS="
	--exclude=_imagingtk*
	--exclude=ImageTk*
	--exclude=SpiderImagePlugin*
	${python36_imaging_CONTENTS}
"
python36_imaging_tk_OBSOLETES="python3-imaging-tk"
python36_imaging_tk_REQUIRES="python36-imaging python36-tkinter"
python36_imaging_tk_CONTENTS="
	usr/lib/python3.6/site-packages/PIL/_imagingtk*
	usr/lib/python3.6/site-packages/PIL/ImageTk*
	usr/lib/python3.6/site-packages/PIL/SpiderImagePlugin*
	usr/lib/python3.6/site-packages/PIL/__pycache__/ImageTk*
	usr/lib/python3.6/site-packages/PIL/__pycache__/SpiderImagePlugin*
"
python37_imaging_REQUIRES="python37 python37-olefile"
python37_imaging_CONTENTS="
	--exclude=_imagingtk*
	--exclude=ImageTk*
	--exclude=SpiderImagePlugin*
	${python37_imaging_CONTENTS}
"
python37_imaging_tk_REQUIRES="python37-imaging python37-tkinter"
python37_imaging_tk_CONTENTS="
	usr/lib/python3.7/site-packages/PIL/_imagingtk*
	usr/lib/python3.7/site-packages/PIL/ImageTk*
	usr/lib/python3.7/site-packages/PIL/SpiderImagePlugin*
	usr/lib/python3.7/site-packages/PIL/__pycache__/ImageTk*
	usr/lib/python3.7/site-packages/PIL/__pycache__/SpiderImagePlugin*
"
python38_imaging_REQUIRES="python38 python38-olefile"
python38_imaging_CONTENTS="
	--exclude=_imagingtk*
	--exclude=ImageTk*
	--exclude=SpiderImagePlugin*
	${python38_imaging_CONTENTS}
"
python38_imaging_tk_REQUIRES="python38-imaging python38-tkinter"
python38_imaging_tk_CONTENTS="
	usr/lib/python3.8/site-packages/PIL/_imagingtk*
	usr/lib/python3.8/site-packages/PIL/ImageTk*
	usr/lib/python3.8/site-packages/PIL/SpiderImagePlugin*
	usr/lib/python3.8/site-packages/PIL/__pycache__/ImageTk*
	usr/lib/python3.8/site-packages/PIL/__pycache__/SpiderImagePlugin*
"
python39_imaging_REQUIRES="python39 python39-olefile"
python39_imaging_CONTENTS="
	--exclude=_imagingtk*
	--exclude=ImageTk*
	--exclude=SpiderImagePlugin*
	${python39_imaging_CONTENTS}
"
python39_imaging_tk_REQUIRES="python39-imaging python39-tkinter"
python39_imaging_tk_CONTENTS="
	usr/lib/python3.9/site-packages/PIL/_imagingtk*
	usr/lib/python3.9/site-packages/PIL/ImageTk*
	usr/lib/python3.9/site-packages/PIL/SpiderImagePlugin*
	usr/lib/python3.9/site-packages/PIL/__pycache__/ImageTk*
	usr/lib/python3.9/site-packages/PIL/__pycache__/SpiderImagePlugin*
"
python_imaging_debuginfo_OBSOLETES="python3-imaging-debuginfo"
PKG_IGNORE="usr/share/doc/python*-imaging-*/"

Re: CI system cryptic error

[Jon Turney]

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

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.

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!

Re: CI system cryptic error

[Hamish McIntyre-Bhatty]

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

Re: CI system cryptic error

[Marco Atzeri]

On 21.01.2022 17:03, Hamish McIntyre-Bhatty wrote:
> 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
> 

I saw something similar but I do not remember the details.

Cygport is looking for something that has changed name or it is not 
available anymore. Probably the old name is still used by Python2 and
it is the reason why the error seldom show up in local build of
maintainers.

cygport --debug should provide some hints

Re: CI system cryptic error

[Hamish McIntyre-Bhatty]

On 22/01/2022 05:34, Marco Atzeri wrote:
> On 21.01.2022 17:03, Hamish McIntyre-Bhatty wrote:
>> 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
>>
> 
> I saw something similar but I do not remember the details.
> 
> Cygport is looking for something that has changed name or it is not 
> available anymore. Probably the old name is still used by Python2 and
> it is the reason why the error seldom show up in local build of
> maintainers.
> 
> cygport --debug should provide some hints

Good idea, I'll try that, and I'll also remove python 2 from my cygwin 
install if I can.

Cheers,

Hamish