CI: show meson-log.txt in Cirrus wheel builds#25440
Conversation
To do this, we need to be able to locate the log file in a fixed location, hence the need to add `build-dir=build` to the flags passed to meson-python. And to make that work, it turns out pypa/build is the better build front-end to use. It's also going to be the future default for cibuildwheel, so this change makes sense anyway. [skip azp] [skip circle]
|
eh oh, trouble with Trying to figure out if this happened before, it should be unrelated to this PR. |
|
A search for that error comes up empty, however we haven't run these wheel builds in 1 months and 8 days I think (that was the last nightly upload for aarch64 to https://anaconda.org/scientific-python-nightly-wheels/numpy/files). That last successful build was before the initial merge of |
|
I guess one issue is that we don't have visibility for when a nightly wheel build fails. |
|
Indeed, that is pretty unhelpful. We could add something like https://cirrus-ci.org/guide/notifications/#email-action, only for failures on |
Yes and no. I'd rather have a visible badge on the scipy/scipy GH landing page rather than getting emailed everyday. |
That would work too perhaps - but I personally am unlikely to notice. After the 2.0 branch split we'll probably go back to weekly cron job triggers instead of daily, so emails wouldn't be too bad. |
|
The Moving ahead with this change, working towards getting the new Accelerate wheel builds in. |
To do this, we need to be able to locate the log file in a fixed location, hence the need to add
build-dir=buildto the flags passed to meson-python. And to make that work, it turns outpypa/buildis the better build front-end to use. It's also going to be the future default forcibuildwheel, so this change makes sense anyway.Extracted from gh-25012, this is a standalone change that is mergeable.
[wheel build]