Skip to content

[automated] Merge branch 'release/8.0' => 'release/8.0-staging' #115577

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

Merged
merged 25 commits into from
Jun 17, 2025

Conversation

github-actions[bot]
Copy link
Contributor

I detected changes in the release/8.0 branch which have not been merged yet to release/8.0-staging. I'm a robot and am configured to help you automatically keep release/8.0-staging up to date, so I've opened this PR.

This PR merges commits made on release/8.0 by the following committers:

  • jozkee
  • vseanreesermsft

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.

merge button instructions

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.

git fetch
git checkout release/8.0
git pull --ff-only
git checkout release/8.0-staging
git pull --ff-only
git merge --no-ff release/8.0

# If there are merge conflicts, resolve them and then run git merge --continue to complete the merge
# Pushing the changes to the PR branch will re-trigger PR validation.
git push https://github.com/dotnet/runtime HEAD:merge/release/8.0-to-release/8.0-staging
or if you are using SSH
git push git@github.com:dotnet/runtime HEAD:merge/release/8.0-to-release/8.0-staging

After PR checks are complete push the branch

git push

Instructions for resolving conflicts

⚠️ If there are merge conflicts, you will need to resolve them manually before merging. You can do this using GitHub or using the command line.

Instructions for updating this pull request

Contributors to this repo have permission update this pull request by pushing to the branch 'merge/release/8.0-to-release/8.0-staging'. This can be done to resolve conflicts or make other changes to this pull request before it is merged.
The provided examples assume that the remote is named 'origin'. If you have a different remote name, please replace 'origin' with the name of your remote.

git fetch
git checkout -b merge/release/8.0-to-release/8.0-staging origin/release/8.0-staging
git pull https://github.com/dotnet/runtime merge/release/8.0-to-release/8.0-staging
(make changes)
git commit -m "Updated PR with my changes"
git push https://github.com/dotnet/runtime HEAD:merge/release/8.0-to-release/8.0-staging
or if you are using SSH
git fetch
git checkout -b merge/release/8.0-to-release/8.0-staging origin/release/8.0-staging
git pull git@github.com:dotnet/runtime merge/release/8.0-to-release/8.0-staging
(make changes)
git commit -m "Updated PR with my changes"
git push git@github.com:dotnet/runtime HEAD:merge/release/8.0-to-release/8.0-staging

Contact .NET Core Engineering (dotnet/dnceng) if you have questions or issues.
Also, if this PR was generated incorrectly, help us fix it. See https://github.com/dotnet/arcade/blob/main/.github/workflows/scripts/inter-branch-merge.ps1.

Mirroring and others added 12 commits April 2, 2025 17:50
…rios (COM, C++/CLI, custom component host) could try to load coreclr from CWD

There is a fallback for apps with no .deps.json where the host will consider the app directory for loading coreclr. In component hosting scenarios, we do not have an app path / directory. We were incorrectly going down the path of looking for coreclr next to the empty app directory, which resulted in looking in the current directory.

This change skips that path for libhost scenarios. It also adds checks that the paths we determine for loading coreclr, hostpolicy, and hostfxr are absolute.
…25-05-13-1454

Merging internal commits for release/8.0
@dotnet-policy-service dotnet-policy-service bot added the linkable-framework Issues associated with delivering a linker friendly framework label May 14, 2025
* Update dependencies from https://github.com/dotnet/emsdk build 20250516.2

Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-8.0.100
 From Version 8.0.17-servicing.25258.1 -> To Version 8.0.17-servicing.25266.2

* Update dependencies from https://github.com/dotnet/emsdk build 20250519.2

Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-8.0.100
 From Version 8.0.17-servicing.25258.1 -> To Version 8.0.17-servicing.25269.2

* Update dependencies from https://github.com/dotnet/emsdk build 20250604.1

Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-8.0.100
 From Version 8.0.17-servicing.25258.1 -> To Version 8.0.18-servicing.25304.1

---------

Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
[manual] Merge release/8.0-staging into release/8.0
vseanreesermsft and others added 4 commits June 10, 2025 13:12
…rios (COM, C++/CLI, custom component host) could try to load coreclr from CWD (#116498)

There is a fallback for apps with no .deps.json where the host will consider the app directory for loading coreclr. In component hosting scenarios, we do not have an app path / directory. We were incorrectly going down the path of looking for coreclr next to the empty app directory, which resulted in looking in the current directory.

This change skips that path for libhost scenarios. It also adds checks that the paths we determine for loading coreclr, hostpolicy, and hostfxr are absolute.

Co-authored-by: Elinor Fung <elfung@microsoft.com>
Co-authored-by: Mirroring <dnceng-mirroring@microsoft.com>
…25-06-10-1311

Merging internal commits for release/8.0
@jozkee jozkee force-pushed the merge/release/8.0-to-release/8.0-staging branch from da98994 to 3293017 Compare June 16, 2025 22:15
@jozkee
Copy link
Member

jozkee commented Jun 17, 2025

75 other jobs are failing and were not displayed due to space limitations.
Builds with failures: [runtime-libraries-coreclr outerloop-windows] [runtime-libraries-coreclr outerloop] [runtime-libraries-coreclr outerloop-linux] [runtime-libraries-coreclr outerloop-osx] [runtime] [runtime-extra-platforms] [runtime-coreclr outerloop] [runtime] [runtime-community]

The build in this PR is in a really bad state, @dotnet/area-infrastructure-libraries, any advice?

@jozkee
Copy link
Member

jozkee commented Jun 17, 2025

runtime-libraries-coreclr outerloop
OSX:

    System.Net.NetworkInformation.Tests.PingTest.Ping_TimedOut_Sync_Success [FAIL]
      Assert.Equal() Failure
      Expected: TimedOut
      Actual:   DestinationNetworkUnreachable

Being addressed by #116631.
Windows:
System.Security.Cryptography.X509Certificates.Tests.RevocationTests.DynamicRevocationTests.TestRevocationWithNoNextUpdate_NotRevoked - Filed #116760, had to close #92423 because it was hiding it.

S.D.Process error is covered by BA.

OS-wide:
OOM errors.

@jozkee jozkee added Servicing-approved Approved for servicing release area-codeflow for labeling automated codeflow NO-SQUASH The PR should not be squashed and removed linkable-framework Issues associated with delivering a linker friendly framework labels Jun 17, 2025
@jozkee
Copy link
Member

jozkee commented Jun 17, 2025

runtime-coreclr outerloop

  • PALTests failed on the first attempt, some passed in the 2nd with a few "The job... ran longer than the maximum time of 60 minutes"
  • All other errors are known in BA

@jozkee
Copy link
Member

jozkee commented Jun 17, 2025

/ba-g see above comments

@jozkee jozkee merged commit 7af93f5 into release/8.0-staging Jun 17, 2025
326 of 408 checks passed
@jozkee jozkee deleted the merge/release/8.0-to-release/8.0-staging branch June 17, 2025 22:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-codeflow for labeling automated codeflow NO-SQUASH The PR should not be squashed Servicing-approved Approved for servicing release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants