I think I've been seeing bad compilations when usi...

# compiler

[Tim McCormack]

I think I've been seeing bad compilations when using kotlin.compiler.incremental in my JVM project -- old code being included in the compilation, or rather, not being recompiled when I do mvn test. I don't think this was happening a few months ago. Is incremental compilation supposed to be stable enough at this point where I shouldn't be seeing such things, or is it that experimental? :-)

[Tim McCormack]

It's also possible that something has changed in my environment, or there's a mismatch between mvn compilations from the command line and what's happening when IntelliJ compiles, or some change in IntelliJ... and obviously it's incredibly difficult to reproduce this behavior, except that when I do mvn clean test suddenly things start working again.

[dmitriy.novozhilov]

cc @Aleksei Cherepanov

[Evgenii Mazhukin]

@Tim McCormack Hello, sorry for late reply. Did you notice any patterns that would help us reproduce the issue?

It'd be perfect if you have a repository with sample project and a way to trigger the incorrect incremental compilation.

[Tim McCormack]

Obviously I didn't see this until many months later... 😅 For reference, I was seeing this in commit 1f7673b8e5a225c320382eea58363c1e51bb63dd (and earlier) of https://codeberg.org/cavern/spelunk/src/commit/ -- but I've since switched to language version 2.0 where incremental compilation isn't supported anyhow.

[Tim McCormack]

I wasn't able to come up with a reliable reproduction case, unfortunately.

[Aleksei Cherepanov]

Thank you for your response. No worries about the delay! If you encounter any similar issues in the future or if you have any other feedback, please don't hesitate to reach out. The most useful information will be the initial commit and the breaking change