Try making PyPy 7.3.9 - Githubissues

conda-forge / pypy3.6-feedstock

A conda-smithy repository for pypy3.6.

BSD 3-Clause "New" or "Revised" License

4 stars 13 forks source link

Try making PyPy 7.3.9 #78

Closed lithomas1 closed 2 years ago

lithomas1 commented 2 years ago

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

conda-forge-linter commented 2 years ago

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

lithomas1 commented 2 years ago

@conda-forge-admin please rerender

github-actions[bot] commented 2 years ago

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/pypy3.6-feedstock/actions/runs/2083015623.

mattip commented 2 years ago

The remaining patches will require some adjustment. One way to get this going would be to locally run

conda build -m .ci_support/linux_64_name_suffix3.8openssl1.1.1.yaml recipe

and

conda build -m .ci_support/linux_64_name_suffix3.9openssl1.1.1.yaml recipe

and then hack away until the patching succeeds.

lithomas1 commented 2 years ago

@conda-forge-admin, please rerender

mattip commented 2 years ago

Thanks

lithomas1 commented 2 years ago

Hmm. It doesn't look like the packages got uploaded for this PR, and I'm not sure what went wrong. Maybe re-triggering the CI will do it?

h-vetinari commented 2 years ago

Unfortunately this has been happening occasionally. A manual restart in Azure can only be done by core members, but it works to push a dummy commit (e.g. git commit --allow-empty -m "retrigger CI") to main (can be done by feedstock maintainers).

Also - depending on the importance of 7.3.9 vs. 7.3.8 -, we should kindly ask who can rebuild aarch/ppc, because those builds cannot be done in CI (previously this was always done by @isuruf AFAIK).

mattip commented 2 years ago

I would suggest holding off with the aarch64/ppc builds and rerunning this. Due to an issue with GenericAlias, which PyPy fixed yesterday, I will add a new patch here.