Closed valeriocos closed 5 years ago
Maybe there are no breaking changes @tdegueul ? If this is the case, could you point me to a couple of projects were breaking changes should be detected? thanks
I just had a quick look out of curiosity (and I woke up with some energy). An unexpected bug is triggered in the Eclipse Java Compiler, possibly because we use it just a bit differently than normally. The bug was reported earlier here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=474080
java.lang.String
can not be resolved by the Eclipse Java compiler, these kinds of NPEs can be expected. Just to be sure. I think more things would go wrong though..I could reproduce the bug here.
The workaround in 88dbcf4f231765dd2b8ff4ac63dfb31be1d1068d is to assign a dummy m3(|unknown:///)
model to the files we couldn't parse, record the error, and let the process continue for the other files. It happens with 3 of the 11k Java files in elastic/elasticsearch
.
The platform can "successfully" build M3 models for Elasticsearch now, but the creation of delta models on which we rely to compute API metrics still takes way too much time (> 1 hour). I'm on it.
Thank you @tdegueul @jurgenvinju for working on it
@valeriocos I expect this to be fixed; please re-open if it isn't!
I'm analysing https://github.com/elastic/elasticsearch (from 01/01/2019 - 01/06/2019) with the following metric providers:
A NPE popped out on
RascalMetricProvider (Number of breaking changes)
(see below).