-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
MutinyTest#testSSE can be unstable #11687
Comments
/cc @cescoffier |
As nothing change in Mutiny around that, it might be a recent change in RestEasy (CC @stuartwdouglas ) |
@cescoffier I think you meant @asoldano I have nothing to do with RESTEasy :-) |
@cescoffier are you able to tell the RESTEasy version upgrade that might be related to this? |
@asoldano It's a total mystery. Our investigations (from @loicmathieu and myself) have shown that it requires the item emitted by the What's not clear is why does it start failing now, while nothing changed except the CI that because a tiny bit faster. @FroMage offered his help too. |
The cause might be different. After a few green runs, it failed again... so might not be a thread issue. |
- Fixes quarkusio#11687 - Moved JAX-RS ClientBuilder service file for native to RESTClientProcessor - Use existing ResteasyProviderFactory to register client providers with if it exists, and don't replace the provider directly
- Fixes quarkusio#11687 - Moved JAX-RS ClientBuilder service file for native to RESTClientProcessor - Use existing ResteasyProviderFactory to register client providers with if it exists, and don't replace the provider directly
- Fixes quarkusio#11687 - Moved JAX-RS ClientBuilder service file for native to RESTClientProcessor - Use existing ResteasyProviderFactory to register client providers with if it exists, and don't replace the provider directly
Just got this failure on CI. Don't know if the timeout is just not enough or if there is a more problematic issue.
I disabled the test for now.
In this run https://github.com/quarkusio/quarkus/pull/11679/checks?check_run_id=1038350811 , I got the error for both the JDK 14 build and the Windows build.
The text was updated successfully, but these errors were encountered: