Skip to content
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

[search] Flaky tests in weekly runs #19148

Closed
ShivangiReja opened this issue Mar 2, 2021 · 2 comments
Closed

[search] Flaky tests in weekly runs #19148

ShivangiReja opened this issue Mar 2, 2021 · 2 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. Search test-reliability Issue that causes tests to be unreliable

Comments

@ShivangiReja
Copy link
Member

ShivangiReja commented Mar 2, 2021

Search tests fail in weekly runs with:

Error Message:
Expected exception of type RequestFailedException, not Microsoft.VisualStudio.TestPlatform.TestHost.DebugAssertException: Method failed with '', and was translated to Microsoft.VisualStudio.TestPlatform.TestHost.DebugAssertException to avoid terminating the process hosting the test.
at Microsoft.VisualStudio.TestPlatform.TestHost.TestHostTraceListener.ShowDialog(String stackTrace, String message, String detailMessage, String )
at Azure.Core.Pipeline.ClientDiagnostics.ExtractFailureContent(String content, ResponseHeaders responseHeaders, String& message, String& errorCode, IDictionary2& additionalInfo) in /_/sdk/search/Azure.Search.Documents/src/Utilities/ClientDiagnostics.ExtractFailureContent.cs:line 56 at Azure.Core.Pipeline.ClientDiagnostics.CreateRequestFailedExceptionAsync(Response response, String message, String errorCode, IDictionary2 additionalInfo, Exception innerException) in /
/sdk/core/Azure.Core/src/Shared/ClientDiagnostics.cs:line 56
at System.Threading.Tasks.ValueTask1.get_Result() at Azure.Search.Documents.DocumentsRestClient.AutocompletePostAsync(AutocompleteOptions autocompleteRequest, CancellationToken cancellationToken) in /_/sdk/search/Azure.Search.Documents/src/Generated/DocumentsRestClient.cs:line 477 at Azure.Search.Documents.SearchClient.AutocompleteInternal(String searchText, String suggesterName, AutocompleteOptions options, Boolean async, CancellationToken cancellationToken) in /_/sdk/search/Azure.Search.Documents/src/SearchClient.cs:line 1093 at Azure.Search.Documents.SearchClient.AutocompleteAsync(String searchText, String suggesterName, AutocompleteOptions options, CancellationToken cancellationToken) in /_/sdk/search/Azure.Search.Documents/src/SearchClient.cs:line 1067 at Azure.Core.TestFramework.DiagnosticScopeValidatingInterceptor.<>c__DisplayClass2_01.<b__0>d.MoveNext() in /mnt/vss/_work/1/s/sdk/core/Azure.Core.TestFramework/src/DiagnosticScopeValidatingInterceptor.cs:line 64
--- End of stack trace from previous location where exception was thrown ---
at System.Threading.Tasks.ValueTask1.get_Result() at Azure.Core.TestFramework.DiagnosticScopeValidatingInterceptor.ValidateDiagnosticScope[T](Func1 action, String expectedName, String methodName, Boolean strict) in /mnt/vss/_work/1/s/sdk/core/Azure.Core.TestFramework/src/DiagnosticScopeValidatingInterceptor.cs:line 112
at Azure.Search.Documents.Tests.AutocompleteTests.<>c__DisplayClass3_0.<b__0>d.MoveNext() in /mnt/vss/_work/1/s/sdk/search/Azure.Search.Documents/tests/DocumentOperations/AutocompleteTests.cs:line 58
--- End of stack trace from previous location where exception was thrown ---
at Azure.Search.Documents.Tests.SearchTestBase.CatchAsync[T](Func1 action) in /mnt/vss/_work/1/s/sdk/search/Azure.Search.Documents/tests/Utilities/SearchTestBase.cs:line 125 Stack Trace: at Azure.Search.Documents.Tests.SearchTestBase.CatchAsync[T](Func1 action) in /mnt/vss/_work/1/s/sdk/search/Azure.Search.Documents/tests/Utilities/SearchTestBase.cs:line 125

For more details check here:

@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Mar 2, 2021
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Mar 3, 2021
@ShivangiReja ShivangiReja added the test-reliability Issue that causes tests to be unreliable label Mar 3, 2021
@ShivangiReja ShivangiReja added the Client This issue points to a problem in the data-plane of the library. label Mar 3, 2021
@Mohit-Chakraborty
Copy link
Contributor

The above failures were caused in ExtractFailureContent() which had an assertion to fail on nested errors.
I see that the code has been refactored and the assertion is no longer there.
So, we are not seeing failures due to this issue. There is a separate issue about handling nested errors.

@github-actions github-actions bot locked and limited conversation to collaborators Mar 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. Search test-reliability Issue that causes tests to be unreliable
Projects
None yet
Development

No branches or pull requests

2 participants