Skip to content
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

Aggregate report skipped due to NO-SOURCE #327

Open
aalmiray opened this issue Dec 12, 2022 · 1 comment
Open

Aggregate report skipped due to NO-SOURCE #327

aalmiray opened this issue Dec 12, 2022 · 1 comment

Comments

@aalmiray
Copy link

I've followed the docs for configuring pitest for subprojects and the aggregator at the root. I use the Kordamp Plugin suite thus plugins are applied in this way

https://github.com/jreleaser/jreleaser/blob/934b1da1e5b1c190f3d07ae613a9659e95a4682e/settings.gradle#L45-L62

subprojects are configured in this way

https://github.com/jreleaser/jreleaser/blob/934b1da1e5b1c190f3d07ae613a9659e95a4682e/build.gradle#L115-L123

The pitest task for every subproject with tests runs successfully. However, the root fails to aggregate reports. Running the build with -i yields the following

> Task :pitestReportAggregate NO-SOURCE
Skipping task ':pitestReportAggregate' as it has no source files and no previous output files.
:pitestReportAggregate (Thread[Execution worker for ':' Thread 11,5,main]) completed. Took 0.0 secs.
@jmswindle
Copy link

jmswindle commented May 1, 2024

I ran into this same issue. Solution for me was to apply the aggregator plugin after my subproject block.

Looks like the plugin is defining the input files by looking for projects with pitest configured. If you apply the aggregator plugin before configuring pitest in the subprojects, you will get this error stating there are no input files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants