Add "side-log" support to cram tests
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- ocaml
- Domain
- build-system, testing
Research direction
Start by tracing how Dune runs cram tests and prints failure diffs, then inspect the cram test failure path and its CI behavior. Define how a side-log is created and exposed through DUNE_CRAM_LOG, and consider both a file path and file descriptor before implementing output after a failure diff. Done means side-log content is shown for failures without changing normal successful test output.
Written by the indexing model from the issue text.
Description
When a cram tests fail, it would be useful to see additional log output that is not necessarily reproducible. Such as inotify events. This would be especially useful for transient failures, especially when then happen in the CI.
The idea would be to provide a side-log mechanism to cram tests and have Dune print this log after the diff in case of failure. For instance, Dune could set an environment variable DUNE_CRAM_LOG pointing to the side log file (or containing the number of a fd open to the side-log file).
- Dominant language
- OCaml
- Stars
- 1.9k
- Forks
- 500
- Avg merge
- 15h 17m
- Merged PRs (30d)
- 287
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.
More from ocaml/dune
-
cli
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
cli
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
cli
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
describe
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
describe
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Similar issues
-
Needs Design Priority: Wishlist
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
elementary/flatpak-platform#253 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
objectionary/hone-maven-plugin#1060 ·
-
0.kind: build failure
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Update Vish to 1.1.5 Openpackage-update
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oSoWoSo/vOid_Community_repOsitory#144 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100