another aarch64 linux attempt

[rfiorella]

MNT: Re-rendered with conda-build 24.9.0, conda-smithy 3.43.0, and conda-forge-pinning 2024.10.22.08.35.23

Checklist

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

[conda-forge-admin]

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/meta.yaml) and found it was in an excellent condition.

[mwtoews]

For the record, there is no obvious error, just a time-out. From the Travis CI logs for aarch64:

============================= test session starts ==============================
platform linux -- Python 3.13.0, pytest-8.3.3, pluggy-1.5.0
rootdir: $SRC_DIR
collected 5 items

No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received

The build has been terminated

whereas a "successful" build from linux_64 should look like this:

============================= test session starts ==============================
platform linux -- Python 3.13.0, pytest-8.3.3, pluggy-1.5.0
rootdir: $SRC_DIR
collected 5 items

test/test_meshpy.py .....                                                [100%]

=============================== warnings summary ===============================
test/test_meshpy.py::test_tetgen_points
  $PREFIX/lib/python3.13/site-packages/meshpy/tet.py:131: UserWarning: Recommend non-empty 'switches' for crash-free meshing
    warn("Recommend non-empty 'switches' for crash-free meshing")

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
========================= 5 passed, 1 warning in 2.47s =========================

[rfiorella]

@mwtoews Thanks for the comments - I'm not sure what's going on here, but wondering if this is why the other PR had suggested skipping tests on aarch64 CI.

It also hangs in the build_locally.py script for these simulations, even for several hours (so sadly probably not as simple as just increasing the time travis waits for a response). Running pytest -v does show what test it seems to be hanging on test_torus, but it's not clear to me yet why it's stuck.

[mwtoews]

Looking further, I can locally replicate the same issue, hanging on test_torus.

The upstream issue is (possibly?) tracked here: inducer/meshpy#53