From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x32c.google.com (mail-wm1-x32c.google.com [IPv6:2a00:1450:4864:20::32c]) by sourceware.org (Postfix) with ESMTPS id 536C2385840A for ; Sat, 22 Jan 2022 05:34:16 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 536C2385840A Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-wm1-x32c.google.com with SMTP id c2so19462866wml.1 for ; Fri, 21 Jan 2022 21:34:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to:content-transfer-encoding; bh=f9WLY8jougH/tzpNwr9RVAl2wDhAHpR9gBKryaMJse4=; b=IIVElplbwbSCiGy6YznLjkegPhP0Xoz1qNKiMMqdEtLil+zq7LSiHT3D5swCg3i202 sCM05rkHfl250GDba51WOaebcdEzJen8pP1/bRItruXgb70c1wWfv2OBbAdj8yDjDFk9 EvkCmdGzRFGXvgpxQUVoJ/Yzqvs4RcE/MSPO3Uo9nuTHmp94gdvKUzJ4KoG1g23ti4FK Q8Hm0xfsVA8ibdKGSZLyGV64XM5B+TLg7gxKlLEYatZteoAP+gsNLan340kR+9eRkC4o Wzb8BU7o+sZ28WSrhUy3d0tPFT9y+/7+ilzLUfwL20YL3QL4022gq42xjA2sIs8xU2aX q0aA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to :content-transfer-encoding; bh=f9WLY8jougH/tzpNwr9RVAl2wDhAHpR9gBKryaMJse4=; b=t+STkye7uZ7E2LatOGB64CfQAV9fke1rtO1iF0UhwX43NfHF4+7Ja7MQjr1GFxTRDv 54L9fYxpv4/YjD+rvuaPxoTNSumu0w2byVBrBe6AHLdC/MsZX0hbe0pJM1BV9FpsCb5H lX2RJW24SLKLcVyZwnycaUxst0IP7G37EGIGiC2X267m++gkxEAqB7uZcGPk9d9DnDm7 n0cCuSTuouGqSm8Uig+oyV1s2qokemB7TAiiFWkEeOjIA4sIE5H4BUtKyB2c+Thd4mYN upT3h+vuP8ALrqFssRe4iYNgH6xmDngLUmAcDYavT2ci0IWsNvaWPJBiAO6Xm824sQLn x7Gw== X-Gm-Message-State: AOAM533Zh6pmnBJPsrujQdLUNymzzizYi8/1dKZ45mxkTxD9WuqAUcoR znG3SszTfOcMtfFUyjR23/4yLpcdmQs= X-Google-Smtp-Source: ABdhPJwWR28gasCzDrvmzXpIrvQiNDyE/MKZZD44a3zSu6wkjMPhgS9AwqIMg9x/OJYItQL6KLHBJw== X-Received: by 2002:a05:600c:3d15:: with SMTP id bh21mr3221522wmb.91.1642829655091; Fri, 21 Jan 2022 21:34:15 -0800 (PST) Received: from ?IPV6:2003:cc:9f2f:3e1f:2847:c5d1:b7d7:bb79? (p200300cc9f2f3e1f2847c5d1b7d7bb79.dip0.t-ipconnect.de. [2003:cc:9f2f:3e1f:2847:c5d1:b7d7:bb79]) by smtp.gmail.com with ESMTPSA id i13sm15349248wmq.45.2022.01.21.21.34.14 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 21 Jan 2022 21:34:14 -0800 (PST) Message-ID: <070ee63a-e876-6866-2c05-6ba6d2e909e2@gmail.com> Date: Sat, 22 Jan 2022 06:34:13 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: CI system cryptic error Content-Language: it To: cygwin-apps@cygwin.com References: From: Marco Atzeri In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin-apps@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin package maintainer discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2022 05:34:17 -0000 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