Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Compilation error is not thrown from KSPLogger logging error in `1.6.10-1.0.3`

See original GitHub issue

I have a SymbolProcessor which was throwing a KotlinCompilation.ExitCode.Compilation.ExitCode.COMPILATION_ERROR from environment.logger.error() as expected in 1.0.2. I have some unit tests to catch the error, which is now failing with 1.0.3 because it returns KotlinCompilation.ExitCode.Compilation.ExitCode.OK, and the KSPLogger API doesn’t fail the compilation.

Is this intended? If so, is there a more preferred way to fail the compilation?

Issue Analytics

State:
Created 2 years ago
Comments:7 (1 by maintainers)

Top GitHub Comments

3reactions

ting-yuancommented, Feb 23, 2022

Fixed in another way in #865.

1reaction

ting-yuancommented, Feb 18, 2022

Here is a patch to KCT to partially fix this problem: Unfortunately INTERNAL_ERROR is no longer possible; Any previous INTERNAL_ERROR in KSP becomes COMPILATION_ERROR until the fix lands in Kotlin compiler and KSP switches back.

I cannot think of any workaround in processors or outside of kotlin-compile-testing, because KSP always returns OK. It returns OK even when processor throws an exception.