init_app_build_backend_maturin test timed out on macOS

[zanieb]

--- STDERR:              uv::it init::init_app_build_backend_maturin ---

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Unfiltered output ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
----- stdout -----

----- stderr -----
Initialized project `foo`

────────────────────────────────────────────────────────────────────────────────


     TIMEOUT [  90.027s] uv::it init::init_lib_build_backend_maturin

[konstin]

Can you see where it got stuck?

[zanieb]

Unfortunately no, that's all I got.

[zanieb]

Here's another https://github.com/astral-sh/uv/actions/runs/11446571344/job/31855447015 also macOS

[zanieb]

Wow these tests are just insanely slow to begin with

        SLOW [  46.554s] uv::it init::init_app_build_backend_maturin
        SLOW [  45.017s] uv::it init::init_lib_build_backend_maturin

I bet it's just a bit slower sometimes and times out. It runs in 7s on my machine — I couldn't reproduce a timeout locally. Regardless, this just seems like an unacceptably slow unit test.

[konstin]

We can speed them up by switching to cffi (no rust deps), pyo3 is quite slow to compile in an uncached integration test (PyO3/maturin#2272).

[zanieb]

I'm not sure how to do that, but that makes sense to me.

[davidhewitt]

Was part of the problem that the tests were building release binaries? I wonder if setting MATURIN_PEP517_ARGS=--profile=dev might have helped if so.

[konstin]

At least in the maturin test suite itself, even building with dev is slow, and the cache artifacts would be too large to store (PyO3/maturin#2272)