-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invoking Task#getAllJvmArgs()
in the build script causes the test JVM to crash if the jacoco
plugin is applied
#28906
Comments
It had quite unpleasant consequences for IDEA 2024.1 release: IDEA-344011 |
The issue is in the backlog of the relevant team and is prioritized by them. |
This is not an issue with the Tooling API, but the way the I was able to reproduce the issue with the reproducer above, using the following command
When the first:
second:
|
Also, note that the test JVM crashing with an initialisation error.
|
Task#getAllJvmArgs()
in the build script causes the test JVM to crash if the jacoco
plugin is applied
Is this a new behavior (in 8.5?) or is there a version where this was known to work? |
The problem is present for quite a while. I was able to reproduce the problem with the sample project above using Gradle 7.0. |
The issue has been fixed in the latest IntelliJ release (2024.1.1). I think the least we should do is to clearly document the side effects of calling |
OK, I didn't think this was new behavior either. This isn't particular to There are three things going on here:
This kind of problem can happen with anything that can extract files with I think to fix this completely, there are a few things we can do:
|
Current Behavior
If the project build script (initscripts are also affected) contains code like this:
Executing such a task via the Gradle Tooling API will result in an daemon crash:
Removal of a such code from the buildscript fixes an error. Test execution from CLI are not affected, error occurs only via Tooling API.
Expected Behavior
The
test
task should be completed without any errors.Context (optional)
No response
Steps to Reproduce
gradle run
via CLIGradle version
any
Build scan URL (optional)
No response
Your Environment (optional)
No response
The text was updated successfully, but these errors were encountered: