wasm32-emscripten CI additions
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.2k
- Forks
- 1k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 66
Description
Future additions for the emscripten CI job:
Well there's a couple more things I'm interested in:
- I'd like to run the tests that mix Rust and C/C++. This is quite common in real packages.
- I'm working on a way to have Pyodide virtual environments https://github.com/pyodide/pyodide/pull/2976 this will lead to rather more graceful testing.
Originally posted by @hoodmane in https://github.com/PyO3/pyo3/issues/2412#issuecomment-1221315962
- Test async support after #3540
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the wasm32-emscripten CI job and reviewing how its current tests are configured. Check how tests mixing Rust with C/C++ are represented, how Pyodide virtual environments relate to testing, and what remains for async support after #3540; done means the listed CI additions are covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust, wasm
- Domain
- build-system, ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100