André Silva

Update here, I think implementing a `org.jacoco.core.internal.analysis.ClassAnalyzer` that takes in several `ExecutionDataStore`'s is the best way. Currently we do a full analysis of the binaries each time a method finishes....

Using `jacoco`, I think the best we can do is https://github.com/STAMP-project/test-runner/pull/112 The only way I see we could achieve a performance similar to GZoltar is to either adapt jacoco so...

Hi @martinezmatias, Another update. I've come to realize that the problem might be that `jacoco` analyzes every single class, not just the ones executed. GZoltar only analyzes the ones that...

I have opened a PR https://github.com/jacoco/jacoco/pull/1212, that introduces an option for skipping non-executed classes in the analysis. This does improve performance, but we are still a bit far from GZoltar....

Test detection might be feasible by using surefire. https://github.com/apache/maven-surefire/tree/surefire-3.0.0-M5_vote-1/surefire-providers https://maven.apache.org/surefire/maven-surefire-plugin/api.html

Hi @martinezmatias > Do you mean to a) retrieve the list with the names of the test methods/classes to execute or b) the test framework from each test? Both. Building...

`test-runner` inter-process communication optimization PR opened in https://github.com/STAMP-project/test-runner/pull/116 > Running flacoco on math70 with this optimization reduces writing/reading time from ~25s to ~3s (~88% reduction).

Running flacoco on `math70` with #82 reduces test detection time from ~60s to ~1s (~99% reduction), as well as fixing #80.

[Fault Localization with Code Coverage Representation Learning](https://arxiv.org/pdf/2103.00270.pdf) Code available: https://github.com/deeprl4fl2021icse/deeprl4fl-2021-icse

This is not an issue with flacoco. The location that is patched through GZoltar is the following: ``` location= org.apache.commons.math.ode.events.EventState line= 175 lineSuspiciousness= 0.107 ``` Flacoco identifies this line, with...