-
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
[automated] Merge branch 'release/7.0-rc1' => 'release/7.0' #74692
[automated] Merge branch 'release/7.0-rc1' => 'release/7.0' #74692
Conversation
System.Runtime.Serialization.Schema isn't getting a NuGet package created for it because it doesn't set IsPackable=true. Co-authored-by: Eric Erhardt <eric.erhardt@microsoft.com>
…otnet#74675) This reverts commit de32c44.
e486741
to
06aceb7
Compare
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
This should be the last "release/7.0-rc-1 -> release/7.0" merge commit backport. It includes only two changes, but there are a lot of CI failures. @lambdageek @dalexsoto @naricc @lewing do you see any concerning failures related to #74675 ? @eerhardt @StephenMolloy @HongGit do you se any concerning failures related to #74597 ? |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
No. All the failures look like Helix infra issues. At least the ones that I checked. |
Ping @lambdageek @dalexsoto @naricc @lewing do you see any concerning failures related to #74675 ? |
/azp run runtime-extra-platforms |
Azure Pipelines successfully started running 1 pipeline(s). |
I don't see anything wrong with this, but I was not able to view the helix logs for some of the failures, which I think is an infrastructure issue. I want to re-run them to make sure. |
|
The failures e.g. on |
the runtime-extra-platforms (Build Browser wasm windows Release LibraryTests) failure is #73721 |
Thanks everyone for checking. Merging now. |
And we will keep an eye on the release/7.0 CI. |
I detected changes in the release/7.0-rc1 branch which have not been merged yet to release/7.0. I'm a robot and am configured to help you automatically keep release/7.0 up to date, so I've opened this PR.
This PR merges commits made on release/7.0-rc1 by the following committers:
Instructions for merging from UI
This PR will not be auto-merged. When pull request checks pass, complete this PR by creating a merge commit, not a squash or rebase commit.
If this repo does not allow creating merge commits from the GitHub UI, use command line instructions.
Instructions for merging via command line
Run these commands to merge this pull request from the command line.
or if you are using SSH
After PR checks are complete push the branch
Instructions for resolving conflicts
Instructions for updating this pull request
Contributors to this repo have permission update this pull request by pushing to the branch 'merge/release/7.0-rc1-to-release/7.0'. This can be done to resolve conflicts or make other changes to this pull request before it is merged.
or if you are using SSH
Contact .NET Core Engineering if you have questions or issues.
Also, if this PR was generated incorrectly, help us fix it. See https://github.com/dotnet/arcade/blob/master/scripts/GitHubMergeBranches.ps1.