IntelliJ IDEA plugin does not support neither multimodule Gradle projects nor Kotlin Multiplatform projects

[lounres]

Try creating multimodule Gradle Kotlin JVM project or Kotlin Multiplatform project and run failing Lincheck-based test. You'll see the "Investigate in Debug Mode" button in the logs of the test. After you click on it, :test Gradle task is run. But in case of multimodule Gradle projects or Kotlin Multiplatform projects there is no such task. So the build quickly fails with

Cannot locate tasks that match ':test' as task 'test' not found in root project 'Lincheck-test'.

* Try:
> Run gradle tasks to get a list of available tasks.
> For more on name expansion, please refer to https://docs.gradle.org/9.0.0/userguide/command_line_interface.html#sec:name_abbreviation in the Gradle documentation.
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to generate a Build Scan (Powered by Develocity).
> Get more help at https://help.gradle.org.

[lounres]

Here is a reproducer for multimodule Gradle Kotlin JVM project: https://github.com/lounres/Lincheck-test

It consists of root and :sub modules. Root module is empty whereas, :sub is configured via Kotlin JVM plugin. There is a simple test in it. (And a stupid bug in sources.) If you run the KoneSundellTsigasMutexConcurrencyTest.modelChecking test, you'll get a failure with the "Investigate in Debug Mode" button. After clicking on it, you'll get the error above.

I use:
Gradle 9.0.0
Kotlin 2.3.0-Beta2
Lincheck dependency 3.3
IntelliJ IDEA IU-252.27397.103
Lincheck plugin 0.20

P.S. Everything works fine with single-module Gradle Kotlin JVM project. There are commented lines for Kotlin JVM and Multiplatform plugins in both root and :sub modules. You can use them to reproduce similar issues (except for Kotlin JVM configuration in the root module).

[lounres]

A small clarification. If you just run the test in debug mode, then the lincheck plugin panels ("Lincheck scenario", "Lincheck State Diagram" and so on) appear. So I guess it is a problem of the "Investigate in Debug Mode" button (that appears in stacktrace) itself. And this works in my another multimodule Gradle Kotlin Multiplatform project.