-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
System.Text.Tests.TranscodingStreamTests.ReadAsync_Memory(bufferLength: 1) failing in CI #60865
Comments
Tagging subscribers to this area: @tarekgh, @dotnet/area-system-text-encoding Issue Details
Configuration:
|
#47444 was tracking the same failure but was closed in August due to no recent occurrences. |
@MattGal we caught two more fish. (BTW, can we include the machine name in the logs? https://dev.azure.com/dnceng/9ee6d478-d288-47f7-aacc-f6e6d082ae6d/_apis/build/builds/1440581/logs/2006) TestResults
| join kind=inner WorkItems on WorkItemId
| join kind=inner Jobs on JobId
| where Finished >= now(-365d)
| where Type == "System.Text.Tests.TranscodingStreamTests"
| where Method == "Read_Span" or Method == "ReadAsync_Memory"
| where Result == 'Fail'
| where QueueName1 == 'ubuntu.1804.armarch.open'
| project Started, Duration, Type, Method, FriendlyName, MachineName, QueueName1, Message, StackTrace, Arguments, Branch
Both single-bit failures, like last time. Both on the SAME machine, ddvsotx2l280, as before. I believe ddvsotx2l280 has a faulty memory stick and should have its memory replaced. The memory check last time probably just isn't as stressful as all the tests we run hour after hour day after day. |
Pretty cheap to do since the work item already contains it and it's already available from the public workitem API, so filed dotnet/arcade#8112. I've taken |
@MattGal do you need this issue to track disposing of this hapless machine ? if not we can close it might be worth even burning the name ddvsotx21280 so that there's no confusion in future. |
https://portal.microsofticm.com/imp/v3/incidents/details/269146909/home tracks disposing the hardware, so we don't need this issue to remain open to prevent it in the future; close as you like. I also verified with DDFUN that the machine has been manually disabled so cannot accidentally come back online. My understanding is that newer machines would just be +1 to the max previous value and/or a totally new naming strategy based off the hardware type (that is, I doubt we'll acquire more TX2s), so I don't think the name needs help to be retired. |
Configuration:
net7.0-Linux-Debug-arm-CoreCLR_checked-(Ubuntu.1804.Arm32.Open)[email protected]/dotnet-buildtools/prereqs:ubuntu-18.04-helix-arm32v7-bfcd90a-20200121150440
Build: https://dev.azure.com/dnceng/public/_build/results?buildId=1440581&view=ms.vss-test-web.build-test-results-tab&runId=41561684&paneView=debug
The text was updated successfully, but these errors were encountered: