Mark Roberts

Here is the log file from running "./randoop_coverage.sh Closure 7 debug 2>&1 | tee test.log": [test.log](https://github.com/rjust/defects4j/files/5380456/test.log) Note that I'm using my fork of defects4j (https://github.com/markro49/defects4j) where I have added support...

Should have mentioned that this subsumes https://github.com/codespecs/daikon/pull/56. That pull request will be deleted/closed as part of this work.

still need to update doc files

As we discussed, I have completed this work and it is ready for review.

I cannot reproduce on our standard linux boxes. I am trying Ubuntu 22.04.3 LTS" (Windows Subsystem for Linux 2) now.

I just realized that it is failing, but in a different way. I get no exceptions, but TestRunner outputs "FAILURE" instead of "SUCCESS". I'll have to look at this more...

That explains the difference, your TestRunner is slightly different than the one you pointed to in the original post. Glad that's sorted.

The problem is using JUnitCore.run(request) instead of JUnitCore.main(args). run(request) takes a path through JUnit that we don't recognize as being part of JUnit so we generate the wrong instrumentation. org.junit.runner.JUnitCore...

Unfortunately, there is no easy fix for this situation. The call to ClassForName on the tests class causes it to be loaded (and thus instrumented) before there is any reference...

I have figured out how to make this work. With today's merge of pull request 548, your original test case now runs to success.