Open gashcrumb opened 1 year ago
A different test failure I hit, but it still seems like catalog related
I get similar flakiness with the vscode test runner from within the IDE as well at least.
@igarashitm if you run mv test -Dtest=CatalogSanityChecks
in the api
module does that work for you? It fails for me here for both tests it runs always.
With #713 this seems better.
🚨This issue has been automatically marked as stale because it has not had recent activity.🚨 If you are still interested in this issue, please, leave a comment stating its current status. Note that if no development resources has been allocated on it, you may need to search for alternative resources to complete it. It will be closed if no further activity occurs. Thank you for your contributions.
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:
1)
rm -rf ~/.m2
2) inkaoto-backend
rungit clean -f -X .
to clean out all non-tracked files 3)mvn 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:
https://github.com/KaotoIO/kaoto-backend/issues/495 https://github.com/KaotoIO/kaoto-backend/issues/494