Skip to content

Conversation

@gsmet
Copy link
Member

@gsmet gsmet commented May 13, 2025

Also optimize things a bit when we don't have tests around.

Fixes #47794

Also optimize things a bit when we don't have tests around.

Fixes quarkusio#47794
Copy link
Contributor

@holly-cummins holly-cummins left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It'd be ideal to have an integration test for this, since it might bite us again, but changes look good!

@gsmet
Copy link
Member Author

gsmet commented May 13, 2025

@holly-cummins you are probably more familiar with this part so feel free to push a test. I agree it would have value.

@holly-cummins
Copy link
Contributor

@holly-cummins you are probably more familiar with this part so feel free to push a test. I agree it would have value.

I don't have the right permissions to be able to push to your branch, so I've (with some regret) created a new PR: #47833

I've confirmed the tests fail in the right way without your changes, and pass with your changes. We don't have many tests for continuous testing in gradle, so it was a bit of a pain to get right. In fact, we didn't have any tests for continuous testing in gradle until @Ladicek added some a while ago, so I was happy to be able to leverage @Ladicek's work. :)

@gsmet gsmet merged commit 5f834a5 into quarkusio:main May 13, 2025
54 of 55 checks passed
@quarkus-bot quarkus-bot bot added this to the 3.23 - main milestone May 13, 2025
@gsmet gsmet modified the milestones: 3.23 - main, 3.22.3 May 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Quarkus 3.22 - Gradle Unit Tests do not run in multi module setup when not all modules have a test

2 participants