Skip to content
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/7.0] Update dependencies from dotnet/emsdk #75652

Merged

Conversation

dotnet-maestro[bot]
Copy link
Contributor

@dotnet-maestro dotnet-maestro bot commented Sep 15, 2022

This pull request updates the following dependencies

From https://github.com/dotnet/emsdk

  • Subscription: 68df92bc-29da-47e1-6f60-08da7ef6374d
  • Build: 20220926.2
  • Date Produced: September 26, 2022 10:54:28 AM UTC
  • Commit: 77c2667993976295017e2759f075550bcf606fc1
  • Branch: refs/heads/release/7.0

…14.3

Microsoft.NET.Workload.Emscripten.net6.Manifest-7.0.100 , Microsoft.NET.Workload.Emscripten.net7.Manifest-7.0.100
 From Version 7.0.0-rc.2.22459.3 -> To Version 7.0.0-rtm.22464.3
@dotnet-issue-labeler dotnet-issue-labeler bot added the area-codeflow for labeling automated codeflow label Sep 15, 2022
@carlossanlop
Copy link
Member

carlossanlop commented Sep 15, 2022

I should probably close this one and wait for the RC2 one to get merged first, then wait for the bot to automatically backport it to release/7.0. Objections? @ViktorHofer @lewing @akoeplinger @steveisok @akoeplinger

@carlossanlop
Copy link
Member

Actually, I should first ask - Do we want to take more emsdk deps changes in RC2?

@lewing
Copy link
Member

lewing commented Sep 19, 2022

The only thing that has changed recently in emsdk is workload packaging and branding and we are definitely taking those changes. I've made sure Jacques workload packaging changes are in both rc2 and rtm now so there will be new flow here as well, and all the in-progress emsdk flow should land.

dotnet-maestro bot and others added 2 commits September 19, 2022 05:05
…18.1

Microsoft.NET.Workload.Emscripten.net6.Manifest-7.0.100 , Microsoft.NET.Workload.Emscripten.net7.Manifest-7.0.100
 From Version 7.0.0-rc.2.22459.3 -> To Version 7.0.0-rtm.22468.1
@steveisok steveisok self-requested a review September 20, 2022 15:15
@carlossanlop
Copy link
Member

@steveisok @lewing @radical there are still many failures. Also, I don't know if the legs are stuck or they got restarted. Can you please take a look?

@lewing
Copy link
Member

lewing commented Sep 20, 2022

@carlossanlop all CI on mac hosts appears to be getting throttled on github, it isn't specific or related to this pr (that just takes packaging updates)

@steveisok
Copy link
Member

Details

Looks like we're being throttled, unfortunately.

@carlossanlop
Copy link
Member

Closing and reopening to re-run CI, since this hit the Apple OS problem heavily.

@lewing
Copy link
Member

lewing commented Sep 24, 2022

runtime-staging (Build Browser wasm windows Release LibraryTests_AOT) failure is #76110 which is concerning but not due to this pr

@lewing
Copy link
Member

lewing commented Sep 24, 2022

runtime (Build Browser wasm Linux Release AllSubsets_Mono_RuntimeTests) is #75391

@lewing
Copy link
Member

lewing commented Sep 24, 2022

coreclr failure looks like #74388 (and can't possibly be related)

…26.2

Microsoft.NET.Workload.Emscripten.net6.Manifest-7.0.100 , Microsoft.NET.Workload.Emscripten.net7.Manifest-7.0.100
 From Version 7.0.0-rc.2.22465.1 -> To Version 7.0.0-rtm.22476.2
@carlossanlop
Copy link
Member

The single failure after latest CI re-run is #75611 (unrelated).

Infra only change, signed off, ready to merge. :shipit:

@carlossanlop carlossanlop merged commit 4bd3ee5 into release/7.0 Sep 26, 2022
@carlossanlop carlossanlop deleted the darc-release/7.0-57867a7e-2156-48ae-a100-a69cfbf28240 branch September 26, 2022 18:22
@ghost ghost locked as resolved and limited conversation to collaborators Oct 26, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-codeflow for labeling automated codeflow
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants