Update Utility task for Jmeter test to show proper error message for … #14727
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@anshii03 The second screenshot shows that the JMeter task not validated completely, it failed to establish the connection with ADO account. Can you please do the needful and update this screenshot after validating scenario (shutdown flag disabled) ? |
ganesp
requested changes
Apr 14, 2021
ganesp
approved these changes
Apr 14, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We want the CLT tasks to fail gracefully with proper error message indicating that the service is now shutdown.
Task name: Apache Jmeter Task
Description: Catching proper error message and displaying so that customer knows that service is now shutdown.
Documentation changes required: N
Added unit tests: (Y/N) N
Attached related issue: (Y/N) [https://dev.azure.com/mseng/AzureDevOps/_workitems/edit/1831804]
Logs for cltabc account where cltshutdown is enabled :
Logs for clttestsu0 account where cltshutdown is disabled :
Checklist: