the .cirrus.star script should always run the tools/ci/cirrus_general.yml tasks on any trigger except if the commit message has [skip ci], [skip cirrus] in the commit message. There are no branch restrictions, but it is limited to the numpy/numpy repository.
The linux_aarch64 task will run for any trigger.
The wheels_upload task will also run for any trigger.
If the trigger is a tag push then CIRRUS_TAG should be defined. This should cause IS_PUSH to be set to true. A debug step might be to echo CIRRUS_TAG to the log.
You should be able to detect from the CI log if IS_PUSH is set because the upload environment variables should be echoed to the log. One should also see push and tag event' being echoed. The first debug step is to look for those echoed variables in the CI log from a pushed tag. If IS_PUSH isn't set then some more detective work is required.
The next step of debugging is to check whether the upload_wheels function works properly. Given that the nightly upload works, I wonder if the NUMPY_STAGING_UPLOAD_TOKEN is correctly configured?

With CI debugging I normally do the majority of the legwork on my own fork. (changing .cirrus.star to run on andyfaff/numpy). This would allow you to make as many tags as you like, allowing you to verify all the way up to the upload step.

Uh oh!

Cirrus fails to upload wheels on tag push. #22730

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions