-
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
HttpStress.csproj fails to build again #51117
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @dotnet/ncl Issue DetailsAccording to the log a change between #50265 and #50244 broke the HttpStress builds: The error we see is the following:
@ViktorHofer any hints?
|
Taking a look now |
Without a binlog (which isn't produced nor uploaded) this is really hard to diagnose. |
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:
|
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). |
I managed to track this to #50166 with git bisect. Setting #50166 might be concerning regarding the ability of using .NET 6 with /cc @adamsitnik |
I see it has been addressed in #51151, trying again with fresh main. |
#51151 fixed this, looks like an exceptional case (a library bug broke the SDK). @ViktorHofer thanks for your support! |
@antonfirsov thank you for the confirmation! |
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:
@ViktorHofer any hints?
The text was updated successfully, but these errors were encountered: