You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
System.Net.Tests.HttpWebRequestTest_Async.GetResponseAsync_ParametersAreNotCachable_CreateNewClient test fails #100912
Build: 🔎https://dev.azure.com/dnceng-public/public/_build/results?buildId=717524 Error message validated:[GetResponseAsync_ParametersAreNotCachable_CreateNewClient.*FAIL]] Result validation: ❌ Known issue did not match with the provided build. Validation performed at: 7/3/2024 10:43:30 AM UTC
changed the title [-]System.Net.Tests.HttpWebRequestTest_Async.GetResponseAsync_ParametersAreNotCachable_CreateNewClient[/-][+]System.Net.Tests.HttpWebRequestTest_Async.GetResponseAsync_ParametersAreNotCachable_CreateNewClient test fails[/+]on Apr 11, 2024
@v-wenyuxu we hid the dumps above as "off-topic", they are not related to this issue, only the error seems similar. Please create a new separate issue and investigate it if you want to get traction on that. Thanks!
When I look at the kusto data, what I see is this test is failing when ALL RemoteExecutor tests are failing within the test suite. I don't think this is related to HttpWebRequest changes we've made starting of this year. I don't have idea about how RemoteExecutor actually works.
/cc @rzikm
Activity
[-]System.Net.Tests.HttpWebRequestTest_Async.GetResponseAsync_ParametersAreNotCachable_CreateNewClient[/-][+]System.Net.Tests.HttpWebRequestTest_Async.GetResponseAsync_ParametersAreNotCachable_CreateNewClient test fails[/+]v-wenyuxu commentedon Jun 18, 2024
v-wenyuxu commentedon Jun 24, 2024
v-wenyuxu commentedon Jun 25, 2024
karelz commentedon Jun 25, 2024
@v-wenyuxu we hid the dumps above as "off-topic", they are not related to this issue, only the error seems similar. Please create a new separate issue and investigate it if you want to get traction on that. Thanks!
liveans commentedon Jul 3, 2024
When I look at the kusto data, what I see is this test is failing when
ALLRemoteExecutor tests are failing within the test suite. I don't think this is related toHttpWebRequestchanges we've made starting of this year. I don't have idea about howRemoteExecutoractually works./cc @rzikm
liveans commentedon Jul 3, 2024
Closing this in favor of #104366