This repository has been archived by the owner on Nov 27, 2023. It is now read-only.
[BUG] Flaky tests prevent a successful initial build with a clean maven repository and source checkout #708
Comments
A different test failure I hit, but it still seems like catalog related io.kaoto.backend.api.resource.v1.DeploymentsResourceTest.startKameletBindingsTest: java.lang.RuntimeException: Failed to start quarkus
|
I get similar flakiness with the vscode test runner from within the IDE as well at least. @igarashitm if you run |
With #713 this seems better. |
🚨This issue has been automatically marked as stale because it has not had recent activity.🚨 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
The project does not appear to build consistently in a fresh environment due to test failures that occur inconsistently in a few modules, such as
api
,kamelet-support
andcamel-route-support
.To Reproduce
The build consistently fails for me with these steps:
rm -rf ~/.m2
kaoto-backend
rungit clean -f -X .
to clean out all non-tracked filesmvn install
After seeing a test failure, a subsequent
mvn install
may or may not run to completion. I think I've so far always seen success the second time I runmvn install
after the above steps.Environment (please complete the following information):
I think some failures I've seen have been captured already such as:
#495
#494
The text was updated successfully, but these errors were encountered: