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
Resolve issues with dotnet-openapi tests in latest SDK #32686
Comments
Thanks for contacting us. We're moving this issue to the |
- .NET SDKs and Visual Studio's `msbuild` avoid #32686
I'm pretty sure there's nothing to "resolve" here. Testing in #36171 |
@dougbu A subsequent SDK update probably resolved the issue. As I recall, this particular stacktrace was tracked down to an external issue. |
@captainsafia please review #36171. Then we can close this 😀 |
* Handle shortened JSON file in `dotnet openapi` - #35767 - an existing JSON file must be truncated * !fixup! Address nits in changed file - take VS suggestions * Stop skipping `dotnet openapi` tests - .NET SDKs and Visual Studio's `msbuild` avoid #32686 already * !fixup! Address nits in `dotnet openapi` test files - take VS suggestions * Extend `dotnet openapi refresh` tests - include regression test for #35767
* Clean backport of e23fd04 * Handle shortened JSON file in `dotnet openapi` - #35767 - an existing JSON file must be truncated * !fixup! Address nits in changed file - take VS suggestions * Stop skipping `dotnet openapi` tests - .NET SDKs and Visual Studio's `msbuild` avoid #32686 already * !fixup! Address nits in `dotnet openapi` test files - take VS suggestions * Extend `dotnet openapi refresh` tests - include regression test for #35767
Issue is not mentioned in release/3.1 or release/5.0. |
Following the latest SDK bump in #32581, the dotnet-openapi tests are failing due to some issues with the new workload resolution flag.
And when run locally:
Skipping the tests for now to unblock our build issues but we'll need to follow-up on this once we have a resolution in the SDK.
Ref: dotnet/sdk#17461
The text was updated successfully, but these errors were encountered: