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

[workloads] Add Current to the name of the workload manifest #80401

Merged
merged 13 commits into from
Jan 28, 2023

Conversation

steveisok
Copy link
Member

dotnet/sdk@f5cb7e3 introduced a change that would make microsoft.net.workload.mono.toolchain an outdated id in order to work around manifest errors when older previews of the .NET 7 SDK were installed. The unfortunate side effect of this change meant the name of the runtime manifest needs to be changed.

On the main branch, the manifest id will now contain current in the name for the .net version being developed.

dotnet/sdk@f5cb7e3 introduced a change that would make `microsoft.net.workload.mono.toolchain` an outdated id in order to work around manifest errors when older previews of the .NET 7 SDK were installed. The unfortunate side effect of this change means the name of the manifest needs to be changed.

On the main branch, the manifest id will now contain current in the name for the .net version being developed.
@ghost
Copy link

ghost commented Jan 9, 2023

Tagging subscribers to this area: @directhex
See info in area-owners.md if you want to be subscribed.

Issue Details

dotnet/sdk@f5cb7e3 introduced a change that would make microsoft.net.workload.mono.toolchain an outdated id in order to work around manifest errors when older previews of the .NET 7 SDK were installed. The unfortunate side effect of this change meant the name of the runtime manifest needs to be changed.

On the main branch, the manifest id will now contain current in the name for the .net version being developed.

Author: steveisok
Assignees: steveisok
Labels:

area-Infrastructure-mono

Milestone: -

Copy link
Member

@lewing lewing left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you'll have to update

<ShortNames Include="Microsoft.NET.Workload.Mono.ToolChain.">
or the msi name will be too long

@lewing
Copy link
Member

lewing commented Jan 10, 2023

I think we want to do the preview tagging before we do this?

@steveisok
Copy link
Member Author

@lewing
Copy link
Member

lewing commented Jan 26, 2023

@radical please take a look at what we need to do to make wbt happy

@radical
Copy link
Member

radical commented Jan 26, 2023

The generated package is Microsoft.NET.Workload.Mono.ToolChain.Current.Manifest-8.0.100-alpha.1.8.0.0-ci.nupkg, but we are trying to install Microsoft.NET.Workload.Mono.ToolChain.Current.Manifest-8.0.100 package. I will try this out locally.

@radical
Copy link
Member

radical commented Jan 26, 2023

And the message says - Installing manifest: Microsoft.NET.Workload.Mono.ToolChain.Current/8.0.0-ci, with the -ci tag. There is some mix up of the names.

@@ -11,6 +11,7 @@
<PackageVersionNet7>7.0.0</PackageVersionNet7>
<PreReleaseVersionLabel>alpha</PreReleaseVersionLabel>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be changing to preview too?

.. change.

The workload manifest has `.Current` added to the name now. This makes
the older name `microsoft.net.workload.mono.toolchain` invalid. But sdk
still installs this, which breaks the workload.

- As a workaround for the tests, remove manifest directory
- Also, update the name in the `IncludedWorkloadManifests.txt`
@radical
Copy link
Member

radical commented Jan 27, 2023

Needs updated packages from dotnet/emsdk#276 .

@lewing
Copy link
Member

lewing commented Jan 27, 2023

we'll need to update the emsdk subscription and InstalledManifests.txt in dotnet/installer as well

@lewing
Copy link
Member

lewing commented Jan 27, 2023

We're blocking installer now dotnet/installer#15346 (comment)

@radical radical closed this Jan 27, 2023
@radical radical reopened this Jan 27, 2023
@radical
Copy link
Member

radical commented Jan 27, 2023

/azp run runtime

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@lewing
Copy link
Member

lewing commented Jan 27, 2023

installer followup dotnet/installer#15366

Copy link
Member

@lewing lewing left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could update the emscripten version to latest but darc should take care of it

@lewing
Copy link
Member

lewing commented Jan 28, 2023

I reran a couple of lanes but the failures were not related

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants