# Dun runtest problems **URL:** \ **Category:** Ecosystem\ **Created:** [February 8, 2019, 5:50pm UTC](https://discuss.ocaml.org/t/dun-runtest-problems/3300 "2019-02-08T17:50:51Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Mathieu\_DS](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/mathieu_ds/32/1332_2.png) [@Mathieu\_DS](https://discuss.ocaml.org/u/Mathieu_DS)\ **Post date:** [February 8, 2019, 5:50pm UTC](https://discuss.ocaml.org/t/dun-runtest-problems/3300/1 "2019-02-08T17:50:51Z")
I have some tests in code and corresponding runtest. The problem is that those tests are blocking and I would like to know which test is blocking. Running a “dune runtest” we get this useless stuff: Done : 525 / 540 If I do “dune --verbose runtest” then I got some information like the last blocking operation: Running[236]: (cd \_build/default/src/legilogic\_ethereum && .legilogic\_ethereum.inline-tests/run.exe inline-test-runner legilogic\_ethereum -source-tree-root …/… -diff-cmd -) and it is impossible to retrieve information about the specific test that is creating the blocking. Any idea on how to locate the blocking test? Mathieu ---
**Author:** ![rdavison](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/rdavison/32/4321_2.png) [@rdavison](https://discuss.ocaml.org/u/rdavison)\ **Post date:** [February 9, 2019, 12:11am UTC](https://discuss.ocaml.org/t/dun-runtest-problems/3300/2 "2019-02-09T00:11:44Z")
Divide and conquer? Could you comment out tests and then rerun it and see if the behavior still exists? I know it’s not an ideal answer, but perhaps do that and open a ticket in [GitHub.com/ocaml/dune](http://GitHub.com/ocaml/dune) about it. ---
**Author:** ![Mathieu\_DS](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/mathieu_ds/32/1332_2.png) [@Mathieu\_DS](https://discuss.ocaml.org/u/Mathieu_DS)\ **Post date:** [February 9, 2019, 10:31am UTC](https://discuss.ocaml.org/t/dun-runtest-problems/3300/3 "2019-02-09T10:31:15Z")
Well yes divide and conquer is a natural solution and I actually solved my problem. But your answer seems to indicate that there a missing feature in dune and I will report to the place you indicated me. ---
**Author:** ![mseri](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/mseri/32/91_2.png) [@mseri](https://discuss.ocaml.org/u/mseri)\ **Post date:** [February 9, 2019, 12:01pm UTC](https://discuss.ocaml.org/t/dun-runtest-problems/3300/4 "2019-02-09T12:01:14Z")
For blocking tests we used to run `dune runtest —verbose —no-buffer` some time ago to figure out a blocking test. The no buffer made sure that the running test line was printed before blocking. Maybe this could have helped also in your case