when the source tree contains a compilation error, it could end up here.

I observed that when there's a compilation error where a constructor has unresolvable annotation like the following, then that ends up in here, masking the root problem.

class Foo {
    @ThereIsNoSuchAnnotation
    public Foo() { ... }
}