Skip to content

Conversation

@fjtirado
Copy link
Contributor

No description provided.


@Test()
public void waitStartup() {
Assertions.fail("Expected failure to check startup timeout exception");
Copy link
Contributor Author

@fjtirado fjtirado Jun 25, 2025

Choose a reason for hiding this comment

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

This assertion was wrong, causing the test to behave randomly
We want to check that the timeout is properly set, so quarkus should receive the IO (which is guaranted by the setExpectedException) and the test should suceeed, not fail

Copy link
Contributor Author

@fjtirado fjtirado Jun 25, 2025

Choose a reason for hiding this comment

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

I disable the test, it is inherently flaky due to the usage of arbitrary timeout. In my local, setting it to 1 ms always worked, but in CI it always failed (effect what I achieve in my local by setting it to 10000ms, which makes sense, there is not exception since the db has time to start and when setting it to 1ms there should be an exception since DB will take more than that to startup)

@fjtirado fjtirado force-pushed the Fix_#143 branch 2 times, most recently from 133a1b9 to 4e507a6 Compare June 25, 2025 11:12
@fjtirado fjtirado merged commit d6a1393 into quarkiverse:main Jun 25, 2025
1 check passed
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

Successfully merging this pull request may close these issues.

3 participants