build-wasi-reusable ci failed on fork for a few days

[yihong0618]

Bug report

Bug description:

cpython do not failed because cpython disable it.

failed ci example: https://github.com/yihong0618/cpython/actions/runs/19122884946/job/54646805015

error:

  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/home/runner/work/cpython/cpython/Tools/wasm/wasi/__main__.py", line 527, in <module>
    main()
    ~~~~^^
  File "/home/runner/work/cpython/cpython/Tools/wasm/wasi/__main__.py", line 523, in main
    dispatch[context.subcommand](context)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^
  File "/home/runner/work/cpython/cpython/Tools/wasm/wasi/__main__.py", line 118, in wrapper
    return func(context, working_dir)
  File "/home/runner/work/cpython/cpython/Tools/wasm/wasi/__main__.py", line 359, in configure_wasi_python
    call(
    ~~~~^
        configure,
        ^^^^^^^^^^
        env=updated_env(env_additions | wasi_sdk_env(context)),
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        context=context,
        ^^^^^^^^^^^^^^^^
    )
    ^
  File "/home/runner/work/cpython/cpython/Tools/wasm/wasi/__main__.py", line 152, in call
    subprocess.check_call(command, **kwargs, stdout=stdout, stderr=stderr)
    ~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/hostedtoolcache/Python/3.14.0/arm64/lib/python3.14/subprocess.py", line 419, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['../../configure', '--host=wasm32-wasip1', '--build=aarch64-unknown-linux-gnu', '--with-build-python=/home/runner/work/cpython/cpython/cross-build/aarch64-unknown-linux-gnu/python', '--with-pydebug', '--config-cache']' returned non-zero exit status 77.
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
📁 /home/runner/work/cpython/cpython/cross-build/wasm32-wasip1
🌎 Environment changes:
     AR=/opt/wasi-sdk/bin/llvm-ar
     CC=/opt/wasi-sdk/bin/clang
     CONFIG_SITE=/home/runner/work/cpython/cpython/Tools/wasm/wasi/config.site-wasm32-wasi
     CPP=/opt/wasi-sdk/bin/clang-cpp
     CXX=/opt/wasi-sdk/bin/clang++
     HOSTRUNNER=/home/runner/downloader/bin/wasmtime run --wasm max-wasm-stack=16777216 --dir /home/runner/work/cpython/cpython::/ --env PYTHONPATH=/cross-build/wasm32-wasip1/build/lib.wasi-wasm32-3.15
     PATH=/opt/wasi-sdk/bin:/opt/hostedtoolcache/Python/3.14.0/arm64/bin:/opt/hostedtoolcache/Python/3.14.0/arm64:/home/runner/downloader/bin:/usr/lib/ccache:/home/runner/downloader/bin:/snap/bin:/home/runner/.local/bin:/opt/pipx_bin:/home/runner/.cargo/bin:/home/runner/.config/composer/vendor/bin:/opt/google-cloud-sdk/bin:/home/runner/.dotnet/tools:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
     PKG_CONFIG_LIBDIR=/opt/wasi-sdk/share/wasi-sysroot/lib/pkgconfig:/opt/wasi-sdk/share/wasi-sysroot/share/pkgconfig
     PKG_CONFIG_PATH=
     PKG_CONFIG_SYSROOT_DIR=/opt/wasi-sdk/share/wasi-sysroot
     RANLIB=/opt/wasi-sdk/bin/ranlib
     SOURCE_DATE_EPOCH=1762382790
     WASI_SYSROOT=/opt/wasi-sdk/share/wasi-sysroot
❯  ../../configure --host=wasm32-wasip1 --build=aarch64-unknown-linux-gnu --with-build-python=/home/runner/work/cpython/cpython/cross-build/aarch64-unknown-linux-gnu/python --with-pydebug --config-cache
Error: Process completed with exit code 1.

seems this patch bring the error( not sure) -> https://github.com/python/cpython/pull/140810/files
cc @brettcannon

``

CPython versions tested on:

CPython main branch

Operating systems tested on:

macOS

[brettcannon]

It's because the runner was changed to Arm and the cache didn't get cleared by the change automatically. Clear the cache manually and it will work. See the comments in #140810 where it was agreed that this is rare enough to not be worth changing (although if someone really wanted to submit a PR we could review it).

[yihong0618]

It's because the runner was changed to Arm and the cache didn't get cleared by the change automatically. Clear the cache manually and it will work. See the comments in #140810 where it was agreed that this is rare enough to not be worth changing (although if someone really wanted to submit a PR we could review it).

learned that thanks