Skip to content

Conversation

@emscripten-forge-bot
Copy link
Contributor

Beep-boop-beep! Whistle-whistle-woo!

@emscripten-forge-bot emscripten-forge-bot added the Automerge The PR will be automatically merged if CI is green label Nov 7, 2025
@IsabelParedes IsabelParedes added 4.X Emscripten v4.x needs-scipy missing-dep One or more dependencies are not available and removed Automerge The PR will be automatically merged if CI is green labels Nov 7, 2025
@emscripten-forge-bot emscripten-forge-bot added the Needs Human Review The CI is not passing, automerge is disabled label Dec 17, 2025
@emscripten-forge-bot
Copy link
Contributor Author

Either the CI is failing, or the recipe is not tested. I need help from a human.
Ping the maintainers: @hodgestar
If you believe you are wrongly pinned, please comment here or open a PR removing you from the maintainers list.

@hodgestar
Copy link
Contributor

The issue reported by the build is that no builds of scipy >= 1.0 were found:

Resolving host environment:

  Platform: emscripten-wasm32 [__unix=0=0]
  Channels: 
   - file:///home/runner/work/recipes/recipes/output/
   - https://repo.prefix.dev/emscripten-forge-4x/
   - microsoft
   - conda-forge
  Specs:
   - python 3.13.* *_cp313
   - numpy 2.3.*
   - scipy >=1.0
   - emscripten-abi >=4,<5.0a0
Error:   × Failed to resolve dependencies: Cannot solve the request because of: No
  │ candidates were found for scipy >=1.0.
  │ 
  ╰─▶ Cannot solve the request because of: No candidates were found for scipy
      >=1.0.

The SciPy recipe does claim to support 1.14.1 and there is a package for it in the emscripten-forge channel.

However, the SciPy build is for numpy 2.2 and the Specs above require numpy 2.3.

I can't immediately see anything in QuTiP or the QuTiP recipe here that requires numpy 2.3, so I'm not sure what went wrong.

@DerThorsten Any suggestions on where to look next?

@IsabelParedes
Copy link
Member

Hi @hodgestar !

Thanks for checking.

The SciPy recipe does claim to support 1.14.1 and there is a package for it in the emscripten-forge channel.

For emscripten-4x recipes, we have migrated most packages to the emscripten-forge-4x channel. It doesn't seem like there are any issues with solving the environment anymore, but a couple of the tests are failing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

4.X Emscripten v4.x missing-dep One or more dependencies are not available Needs Human Review The CI is not passing, automerge is disabled needs-scipy

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants