Repository navigation
HttpStress.csproj fails to build again #51117
Description
According to the log a change between #50265 and #50244 broke the HttpStress builds:
https://dev.azure.com/dnceng/public/_build/results?buildId=1078046&view=logs&j=2d2b3007-3c5c-5840-9bb0-2b1ea49925f3&t=8ca65746-3bfa-57bf-9141-d805b5d39db5
Call stack:
C:\Program Files\dotnet\sdk\5.0.202\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets(241,5): error MSB4018: The "ResolvePackageAssets" task failed unexpectedly.
System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
at System.IO.Strategies.SyncWindowsFileStreamStrategy.Write(Byte[] buffer, Int32 offset, Int32 count) in /_/src/libraries/System.Private.CoreLib/src/System/IO/Strategies/SyncWindowsFileStreamStrategy.cs:line 64
at System.IO.Strategies.BufferedFileStreamStrategy.Flush(Boolean flushToDisk) in /_/src/libraries/System.Private.CoreLib/src/System/IO/Strategies/BufferedFileStreamStrategy.cs:line 778
at System.IO.Strategies.BufferedFileStreamStrategy.Dispose(Boolean disposing) in /_/src/libraries/System.Private.CoreLib/src/System/IO/Strategies/BufferedFileStreamStrategy.cs:line 167
at System.IO.Stream.Close() in /_/src/libraries/System.Private.CoreLib/src/System/IO/Stream.cs:line 165
at System.IO.BinaryWriter.Dispose(Boolean disposing) in /_/src/libraries/System.Private.CoreLib/src/System/IO/BinaryWriter.cs:line 75
at System.IO.BinaryWriter.Dispose() in /_/src/libraries/System.Private.CoreLib/src/System/IO/BinaryWriter.cs:line 81
at Microsoft.NET.Build.Tasks.ResolvePackageAssets.CacheWriter.WriteToCacheFile()
at Microsoft.NET.Build.Tasks.ResolvePackageAssets.CacheReader.CreateReaderFromDisk(ResolvePackageAssets task, Byte[] settingsHash)
at Microsoft.NET.Build.Tasks.ResolvePackageAssets.CacheReader..ctor(ResolvePackageAssets task)
at Microsoft.NET.Build.Tasks.ResolvePackageAssets.ReadItemGroups()
at Microsoft.NET.Build.Tasks.ResolvePackageAssets.ExecuteCore()
at Microsoft.NET.Build.Tasks.TaskBase.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.ExecuteInstantiatedTask(ITaskExecutionHost taskExecutionHost, TaskLoggingContext taskLoggingContext, TaskHost taskHost, ItemBucket bucket, TaskExecutionMode howToExecuteTask) [C:\app\HttpStress.csproj]
@ViktorHofer any hints?
Activity
ViktorHofer commentedon Apr 12, 2021
Taking a look now
ViktorHofer commentedon Apr 12, 2021
Without a binlog (which isn't produced nor uploaded) this is really hard to diagnose.
antonfirsov commentedon Apr 12, 2021
I have a local repro. How can I get the binlog(s) that can help diagnosing this?
Here is the PR history between the last successful and the first failing CI run, in case any of them is obviously suspicious:
ViktorHofer commentedon Apr 12, 2021
Add /bl to the build command and send me the binlog (name by default is msbuild.binlog) via Teams please (a binlog contains env vars).
antonfirsov commentedon Apr 14, 2021
I managed to track this to #50166 with git bisect. Setting
DOTNET_SYSTEM_IO_USENET5COMPATFILESTREAM=1fixes the issue.#50166 might be concerning regarding the ability of using .NET 6 with
dotnet buildfrom within a Windows docker container./cc @adamsitnik
antonfirsov commentedon Apr 14, 2021
I see it has been addressed in #51151, trying again with fresh main.
antonfirsov commentedon Apr 14, 2021
#51151 fixed this, looks like an exceptional case (a library bug broke the SDK). @ViktorHofer thanks for your support!
adamsitnik commentedon Apr 14, 2021
@antonfirsov thank you for the confirmation!