-
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
TestLauncher cannot run the same test in different test tasks if configuration cache is enabled #26056
Labels
Milestone
Comments
donat
added
a:bug
in:configuration-cache
Configuration Caching
@configuration-cache
labels
Aug 9, 2023
I wrote a quick cross-version test method for
The test output is here
|
This was referenced Oct 17, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current Behavior
Running a test method twice in different test tasks result in the following exception:
Expected Behavior
No Exception.
The configuration cache entry should not be reused if a different test task is specified via the TestLauncher.
Context (optional)
IntelliJ IDEA has support for invoking Gradle tests via the
TestLauncher
API that will be eventually turned on by default. I assigned this issue to the next RC1 milestone as fixing this issue later might delay the adoption further.Steps to Reproduce
gradle.testLauncherAPI.enabled=true
JavaIncrementalCompilationWithCachingIntegrationTest
and run theincremental state is restored from the build cache
with the green play button. Select theembeddedIntegTest
task and observe the passing test.embeddedIntegTest
withforkingIntegTest
.Gradle version
8.4-20230719142735+0000
Build scan URL (optional)
https://ge.gradle.org/s/nnkvf236omh5u
Your Environment (optional)
No response
The text was updated successfully, but these errors were encountered: