-
Notifications
You must be signed in to change notification settings - Fork 597
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
Increase logging level in JMSAsyncSendTests #30126
Increase logging level in JMSAsyncSendTests #30126
Conversation
!libby |
Your personal pipeline request is at https://libh-proxy1.fyre.ibm.com/cognitive/pipelineAnalysis.html?uuid=2c468d14-5243-4bde-af5c-4129f64cf348 Target locations of links might be accessible only to IBM employees. |
Code analysis and actionsDO NOT DELETE THIS COMMENT.
|
Code analysis and actionsDO NOT DELETE THIS COMMENT.
|
!libby |
Your personal pipeline request is at https://libh-proxy1.fyre.ibm.com/cognitive/pipelineAnalysis.html?uuid=3d4d84c0-ac07-4882-8ae6-c4f3353a7ca8 Target locations of links might be accessible only to IBM employees. |
Code analysis and actionsDO NOT DELETE THIS COMMENT.
|
release bug
label if applicable: https://github.com/OpenLiberty/open-liberty/wiki/Open-Liberty-Conventions).There are some issues in the AsyncSend tests in the messaging clientcontainer test project.
These are intermittent and probably timing issues related to running tests concurrently.
The default logging in the test makes it difficult to triage and diagnose problems in the tests, so this change is simply to change the level at which some of the test information is logged. This should help future problem analysis.