`dune build @check` should pass if `dune build @all` does
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 1.9k
- Forks
- 500
- Avg merge
- 15h 21m
- Merged PRs (30d)
- 277
Description
I'm working on improving the build system in ahrefs' monorepo. Part of this work is allowing to build as many things as possible in one command, and to speed up the feedback loop from dune. dune build @all tends to be pretty slow, even in subparts of the monorepo. So I wanted to use dune build @check instead, at least during development. But there are directories where dune build @check doesn't pass, while building the @all alias is successful. It feels like a bug, given that @check should be a subset of @all.
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 reproducing the discrepancy in the affected monorepo directories with dune build @check and dune build @all, comparing which targets or errors differ. The work is done when @check succeeds wherever the corresponding @all build succeeds, with regression coverage for the identified case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100