-
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
Remove stacktraces from exceptions thrown deliberately in RESTEasy Reactive tests #19579
Conversation
This workflow status is outdated as a new workflow run has been triggered. Failing Jobs - Building 5736e48
Full information is available in the Build summary check run. Test Failures⚙️ JVM Tests - JDK 11 Windows #📦 extensions/resteasy-reactive/quarkus-resteasy-reactive/deployment✖
|
…active tests This is done so developers looking at the output of tests will not be tricked by false negatives
5736e48
to
4dc12b9
Compare
Failing Jobs - Building 4dc12b9
Full information is available in the Build summary check run. Test Failures⚙️ JVM Tests - JDK 11 Windows #📦 extensions/resteasy-reactive/quarkus-resteasy-reactive/deployment✖
|
@stuartwdouglas this seems very suspicious:
Perhaps it has to do with the latest changed made to the |
I was going to take a more general approach to fixing this with the filtering approach I outlined in the quarkus-dev post. In addition this does not seem to actually work, locally I see:
The test is expected to fail, so it still passes, but this is something that would be picked up by the more general logging approach. |
I will backport it as all the future tests will be a pain. |
Hum, I just saw @stuartwdouglas 's message. I'll fix the test instead. |
I think Stuart already fixed it in another PR |
This is done so developers looking at the output of tests will not be tricked
by false negatives