-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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
[release/8.0] Use MacOS-13 in CI #58549
Conversation
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
@dotnet/source-build any idea why the global.json changes in this PR would cause a JSON parsing error, only in the source-build job? The JSON in global.json does appear to be valid, so not sure what's going on |
I suspect it's because the trailing newline was removed from the end of the file. I added it back. |
Interesting, is that a known thing w/ how SourceBuild parses global.json? I'm curious why it only happened there |
Not specific to source build. It's a general Linux thing. Certain Linux tools do not play nicely with files formatted that way. That's why GitHub has UI that alerts you to a missing newline. So likely source build is executing something in the context of Linux that doesn't like this. |
Failures unrelated |
No description provided.