Given an artifact like cpython-3.8.19-x86_64-pc-windows-msvc-shared-pgo-20240401T1106.tar.gz, we were matching against the triple x86_64-pc-windows-msvc (rather than x86_64-pc-windows-msvc-shared); so the release code then assumed that the install suffix was shared-pgo rather than pgo, and failed to align the assets.
This should fix both of the issues described in #244, since the hard-float armv7 triples are also prefixes of the non-hard-float variants (armv7-unknown-linux-gnueabihf vs. armv7-unknown-linux-gnueabi).
Test Plan
Ran just release with these local changes (skipping uploads); verified that no missing-file errors were raised.
Summary
Given an artifact like
cpython-3.8.19-x86_64-pc-windows-msvc-shared-pgo-20240401T1106.tar.gz, we were matching against the triplex86_64-pc-windows-msvc(rather thanx86_64-pc-windows-msvc-shared); so the release code then assumed that the install suffix wasshared-pgorather thanpgo, and failed to align the assets.This should fix both of the issues described in #244, since the hard-float armv7 triples are also prefixes of the non-hard-float variants (
armv7-unknown-linux-gnueabihfvs.armv7-unknown-linux-gnueabi).Test Plan
Ran
just releasewith these local changes (skipping uploads); verified that no missing-file errors were raised.