Repository navigation
Fix Camel-Spring-Boot Daily #428 test failure: add CamelHibernateIT - #2063
Merged
Merged
Conversation
Add CamelHibernateIT for the new camel-hibernate-starter so the CamelCatalogIT coverage check passes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CamelCatalogIT.allComponentsCoveredfails on the Camel-Spring-Boot Daily build on main (#427, #428) with:camel-hibernate-starterwas added in daaaa75 without the matching integration test. This addsCamelHibernateIT, following the standard generated pattern. It needs no extra configuration, because the component is created but not started (same asCamelJpaIT).Verified locally:
CamelCatalogITfails with exactlycamel-hibernate-starter (hibernate);CamelCatalogITandCamelHibernateITpass.Not addressed here:
NamedCassandraAggregationRepositoryIT.testGetNotExistsfailed once in Camel spring boot 3.7.x local build v2 #427 ("Query timed out after PT5S"); it looks like a flaky test (5s client timeout, with a TRUNCATE before each test).