It gets rid of a warning message so I thought I'll keep it for now. I'll merge these patches into the upstream in a future version of REBOUND so that we can get rid of all them.

There's another error: Error: Dynamic linking error: cannot resolve symbol emscripten_sleep :(

I can fix that. But how come I didn't get those errors? And how can I make sure I fix them all?

I can fix that. But how come I didn't get those errors? And how can I make sure I fix them all?

You could run the tests locally with pytest -svra packages/rebound/test_rebound.py – but I usually find the CI logs to be better sometimes, because from a local run I wasn't able to see that the timeout was due to a Pyodide fatal error (this one, in this case).

I'd recommend an out-of-tree build in your CI, too, if that helps and if you're interested: https://pyodide.org/en/stable/development/building-and-testing-packages.html

Thanks. I'm still a bit confused on how to do this properly.

Right now the tests pass locally. If the package compiles and runs fine locally, then why does it not compile in the CI?

Are the two failing CI tests main / test-core (macos-14, selenium, safari) and ci/circleci: test-core-node-nodylink failing because of something in the rebound/reboundx packages? Or is that unrelated?

Those are unrelated, don't worry about them.

CI looks good to me.

Thanks @hannorein!