-
Notifications
You must be signed in to change notification settings - Fork 38.3k
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
AbstractTestContextBootstrapper should not log stack trace when skipping a TestExecutionListener #28962
Comments
The log message you have provided is a If I recall correctly, this has been the case since 2007 when the TestContext framework was first introduced. At that time it was the case for And the Servlet APIs came into play when we introduced support for web application contexts. So, unless you are raising this issue to make some sort of change to the behavior, I think we can close this issue as "works as designed". |
Thanks, but I am very much aware of that.
Here is the log output with Spring Boot
And the log, for the same app, using Spring Boot
|
Yes, I'm confident you're aware of that, but when I discuss issues in public forums I do not treat the discussion as a one-on-one discussion with an individual. Rather, I provide information that may be useful for anyone reading the discussion in order to provide a full picture of the topic at hand. In light of that, please keep in mind that you do not need to thank me or inform me that you are already aware of something.
Thanks for providing the differing log output. That now clarifies why you created this issue. Specifically, the log output has changed in 6.0 milestones due to #28666. I'll update this issue's title to reflect that, and I'll rework the exception handling in |
Creating an empty app on start.spring.io with Spring Boot
3.0.0-SNAPSHOT
and running the test leads to the following DEBUG message including a stack trace:The text was updated successfully, but these errors were encountered: