-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DevMojoIT.testThatNewResourcesAreServed is flaky #16524
Comments
/cc @aloubyansky @geoand |
I have an idea what might be the cause of this issue |
…v-mode This prevents Vert.x from caching static resources Fixes: quarkusio#16524
#16527 should take care of the issue. I used |
Good catch! But why did it not fail every time? |
My assumption is that something changed with Vert.x - maybe it caches for longer. |
Well, a fix is a fix. |
…v-mode This prevents Vert.x from caching static resources Fixes: quarkusio#16524
Ensure that Vert.x runs in its dev-mode when Quarkus is started in dev-mode
Unfortunately, this still happens: #16250 (comment) |
…v-mode This prevents Vert.x from caching static resources Fixes: quarkusio#16524 (cherry picked from commit 36f76f5)
Haven't seen this for a while, closing. |
Actually, I've see this happen, for example in #18363 (comment) |
The problem is that I cannot reproduce the problem locally... |
…he test fails Relates to: quarkusio#16524
…he test fails Relates to: quarkusio#16524
…he test fails Relates to: quarkusio#16524
Use matchers to in flaky DevMojoIT in order to get proper logs when the test fails
Closing this as the test is no longer flaky. |
Seen e.g. here and here:
The text was updated successfully, but these errors were encountered: