Using this repository as a submodule has a large git history
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- git, wasm
- Domain
- build-system, devops
Research direction
Start by examining the Wasmtime submodule integration and the history of the prod/testsuite-base branch. Compare that setup with the proposed CI-generated downloadable artifacts, including how tests would fetch and unpack them. Done means an agreed integration approach reduces clone history while preserving access to the testsuite.
Written by the indexing model from the issue text.
Description
Right now Wasmtime pulls in tests from this repository as a submodule, pinned to the prod/testsuite-base branch. This effectively means, though, that when cloning Wasmtime contributors have to clone the full history of this branch, which is quite large. This branch is added to whenever a wasm binary changes, is added, etc, and wasm binaries are all blobs so there's not the ability to share much between commits (it's a lot of big objects). I wanted to open this as an issue because while it's not the biggest of problems now I think this is going to become a scaling problem at some point.
One possible alternative would be to produce downloadable artifacts from CI or similar from this repository rather than committing all wasm binaries to a branch. Wasmtime's tests could then download and unpack this artifact to run all the tests, which would avoid the need to check binaries into Wasmtime's repo as well. This also isn't necessarily great though as fetching artifacts can be annoying, and there might be a lot of artifacts in this repo (e.g. if they were per-commit).
Overall I'm not sure how best to handle this myself, but I wanted to file an issue regardless in case others have better ideas on integration.
- Dominant language
- Rust
- Stars
- 88
- Forks
- 50
- Avg merge
- 8d 21h
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from WebAssembly/wasi-testsuite
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
WebAssembly/wasi-testsuite#291 ·
-
enhancement good first issue upstream/wasmtime
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
WebAssembly/wasi-testsuite#216 · 1 comment ·
-
bug wasi-sockets
Difficulty 3/5 1-2 days Newbie friendliness 45/100
WebAssembly/wasi-testsuite#215 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
WebAssembly/wasi-testsuite#61 · 3 comments ·
All issues in WebAssembly/wasi-testsuite
Similar issues
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
pbakaus/impeccable#1601 ·
Maintainers usually reply within 1 day
-
RDF/XML writer: a blank node in two lists is left out of the secondPossibly taken @mrnolte claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
phillord/horned-owl#368 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mongodb/kingfisher#588 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug rust
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days