Hey Colvin, I would probably not blame the UI module for that, but it is mentioned in the output. If I understand it correctly, IntelliJ IDEA cannot be used to run the tests as proposed before, because the Kotlin UI module's WebAssembly target is not supported? If that is the case, could you try disabling the UI module and report back? There is a PR for disabling the UI module, but you may have to take a look at the comments as well, as the current state may not diasbling it correctly: https://github.com/apache/solr/pull/3261
It is known that the UI module slowed down our build times, and when built for production it has even longer build times, but as far as I remember, it should not slow down follow-up executions. But you may also try the development mode by setting "production=false" in your gradle.properties file (if not already the case) and see if that makes any difference? Best, Christos On Tue, Apr 8, 2025 at 11:54 PM Colvin Cowie <colvin.cowie....@gmail.com> wrote: > Hey Jason, > > I was using 2024.3.2, updated to 2024.3.5 and it's the same, running on > Windows 10 with Temurin 21.0.5. The intellij issue I linked says it was > raised on 2024.1.4, so perhaps 2023 isn't affected. The compiler issue > shows up like this: > > Executing pre-compile tasks… > Running 'before' tasks > Checking sources > Kotlin: WebAssembly JS is not yet supported in IDEA internal build system. > Please use Gradle to build solr-root.solr.ui.wasmJsMain and tests of > solr-root.solr.ui.wasmJsTest (enable 'Delegate IDE build/run actions to > Gradle' in Settings). > Dependency analysis found 0 affected files > Updating dependency information… [tests of solr-root.solr.core.test] > Parsing java… [tests of solr-root.solr.core.test] > > *java: java.lang.IllegalArgumentException: source level should be in > '1.1'...'1.8','9'...'18' (or '5.0'..'18.0'): 21java: source level should be > in '1.1'...'1.8','9'...'18' (or '5.0'..'18.0'): 21* > Dependency analysis found 0 affected files > Errors occurred while compiling module 'tests of solr-root.solr.core.test' > Running 'after' tasks > Eclipse compiler was used to compile java sources > Finished, saving caches… > Executing post-compile tasks… > Synchronizing output directories… > 08/04/2025 21:45 - Build completed with 2 errors and 1 warning in 1 sec, > 726 ms > > The missing import shows up like this > > C:\Dev\solr\solr\core\src\java\org\apache\solr\util\stats\InstrumentedPoolingHttpClientConnectionManager.java > java: The type org.apache.commons.logging.Log cannot be resolved. It is > indirectly referenced from required type > org.apache.http.impl.conn.PoolingHttpClientConnectionManager > > Cheers > Colvin > > On Mon, 7 Apr 2025 at 14:59, Jason Gerlowski <gerlowsk...@gmail.com> > wrote: > > > Hey Colvin, > > > > Changing the "Run tests using" setting to "IntelliJ IDEA" is the main > > way I know of to tackle the long startup time for tests. (For those > > that might be unfamiliar, the full path in my version of IntelliJ at > > least is: "Settings" -> "Build, Execution, Deployment" -> "Build > > Tools" -> "Gradle" -> "Run tests using") > > > > That said - toggling the settings has always "just worked" in my > > environment (MacOS, IDEA 2023.2.1, OpenJDK Java 21.0.5). I haven't hit > > any of those additional hurdles you mentioned. > > > > Maybe it's something particular to your IntelliJ or Java version? If > > you share those maybe that'd help someone either reproduce or offer a > > workaround? > > > > Best, > > > > Jason > > > > On Mon, Apr 7, 2025 at 7:48 AM Colvin Cowie <colvin.cowie....@gmail.com> > > wrote: > > > > > > Hello all, > > > > > > While writing smoke tests for the v2 API I've noticed that the spin up > > time > > > of the tests in intellij with gradle is quite slow, making it hard to > > > iterate rapidly. Even without making any changes, there's about 30-40 > > > seconds of gradle build before they start running. And it's maybe > double > > > that with changes just to the tests themselves. I'm running on a > > *reasonable > > > *Lenovo P50 (i7-6820HQ,32GB, M.2 SSD) though it is a bit old. > > > > > > I see a similar thread was raised on the Lucene list last year, with > one > > > suggested improvement being to use IntelliJ (really it's the Eclipse > > > Compiler) to build and run rather than Gradle. > > > https://lists.apache.org/thread/9j4s4wqftlbst640z5zzgsddwmqgondj > > > > > > That does seem to make it a bit faster (down to 10-20 seconds). But in > > > order to make it work on main I had to manually download the latest ECJ > > and > > > point at it ( > > > > > > https://youtrack.jetbrains.com/issue/IDEA-355457/Update-Eclipse-ECJ-compiler > > ), > > > and also had to add an extra dependency for the commons logger in Core > > > because IntelliJ didn't resolve it itself. So that's not an ideal > > solution. > > > > > > Does everyone else have the same experience with running things from > > > intellij? Any tips to improve it? > > > > > > Thanks > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org > > For additional commands, e-mail: dev-h...@solr.apache.org > > > > >
