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

[xaprepare] don't install microsoft-net-runtime-android workload #6114

Conversation

jonathanpeppers
Copy link
Member

Context: #6112 (review)

The .NET Preview 7 bump is failing with:

Running: /Users/builder/Library/Android/dotnet/dotnet "workload" "install" "microsoft-net-runtime-android" "--skip-manifest-update" "--verbosity" "diag"
stderr | Workload with id microsoft-net-runtime-android is not recognized.

However, it was a bug in the dotnet workload install command that we
were even able to install this workload in the first place! The
concept behind "abstract" workloads is they are not user visible in
any way. They're meant to be an implementation detail.

In 0150bbb, I setup xaprepare to install
microsoft-net-runtime-android, but we don't actually even need to do
this. We can simply update the sdk-manifest for this pack, so the
version matches $(DotNetRuntimePacksVersion).

microsoft-net-runtime-android will get installed later during the
ExtractWorkloadPacks target:

https://github.com/xamarin/xamarin-android/blob/c1a2ee70214e86757541b5759c9ed54941bd4680/build-tools/create-packs/Directory.Build.targets#L119-L122

Since android and android-aot extend
microsoft-net-runtime-android, this step will install it.

Context: dotnet#6112 (review)

The .NET Preview 7 bump is failing with:

    Running: /Users/builder/Library/Android/dotnet/dotnet "workload" "install" "microsoft-net-runtime-android" "--skip-manifest-update" "--verbosity" "diag"
    stderr | Workload with id microsoft-net-runtime-android is not recognized.

However, it was a bug in the `dotnet workload install` command that we
were even able to install this workload in the first place! The
concept behind "abstract" workloads is they are not user visible in
any way. They're meant to be an implementation detail.

In 0150bbb, I setup `xaprepare` to install
`microsoft-net-runtime-android`, but we don't actually even need to do
this. We can simply update the `sdk-manifest` for this pack, so the
version matches `$(DotNetRuntimePacksVersion)`.

`microsoft-net-runtime-android` will get installed later during the
`ExtractWorkloadPacks` target:

https://github.com/xamarin/xamarin-android/blob/c1a2ee70214e86757541b5759c9ed54941bd4680/build-tools/create-packs/Directory.Build.targets#L119-L122

Since `android` and `android-aot` extend
`microsoft-net-runtime-android`, this step will install it.
@jonpryor jonpryor merged commit c89b4af into dotnet:main Jul 22, 2021
jonpryor pushed a commit that referenced this pull request Jul 22, 2021
Context: #6112 (review)

The .NET Preview 7 bump is failing with:

	Running: /Users/builder/Library/Android/dotnet/dotnet "workload" "install" "microsoft-net-runtime-android" "--skip-manifest-update" "--verbosity" "diag"
	stderr | Workload with id microsoft-net-runtime-android is not recognized.

However, it was a bug in the `dotnet workload install` command that
allowed us to even install this workload in the first place!
The concept concept behind "abstract" workloads is they are not user
visible in any way; they're meant to be an implementation detail.

In commit 0150bbb, I setup `xaprepare` to install the
`microsoft-net-runtime-android` workload, but we don't actually even
need to do this.  We can simply update the `sdk-manifest` for this
pack, so that the version matches `$(DotNetRuntimePacksVersion)`.

The `microsoft-net-runtime-android` workload will get installed later
during the `ExtractWorkloadPacks` target, as part of installing the
`android` or `android-aot` workloads:

https://github.com/xamarin/xamarin-android/blob/c1a2ee70214e86757541b5759c9ed54941bd4680/build-tools/create-packs/Directory.Build.targets#L119-L122

Since `android` and `android-aot` extend
`microsoft-net-runtime-android`, this step will install it.
@jonathanpeppers jonathanpeppers deleted the dotnet-workload-install-microsoft-net-runtime-android branch July 23, 2021 01:58
thaystg added a commit to thaystg/xamarin-android that referenced this pull request Jul 23, 2021
…er_unhandled_exception

* origin/main:
  Bump to dotnet/installer@19943da 6.0.100-rc.1.21372.10 (dotnet#6110)
  [xaprepare] don't install microsoft-net-runtime-android workload (dotnet#6114)
  [Mono.Android] Use `mono_unhandled_exception` for NET6 (dotnet#6104)
  Bump to dotnet/installer@9c463710 6.0.100-rc.1.21369 (dotnet#6072)
  Bump to xamarin/xamarin-android-binutils/2.37-XA.1@77618674 v2.37 (dotnet#6096)
  [Mono.Android.Export] Fix DynamicDependency to JavaArray (dotnet#6105)
  [xaprepare] always delete ~/android-toolchain/dotnet (dotnet#6098)
  [CI] Add nuget to msi conversion and VS insert stage (dotnet#6030)
  [build] delete platform-31 folder on test jobs (dotnet#6103)
jonpryor pushed a commit to jonpryor/xamarin-android that referenced this pull request Aug 25, 2021
…net#6114)

Context: dotnet#6112 (review)

The .NET Preview 7 bump is failing with:

	Running: /Users/builder/Library/Android/dotnet/dotnet "workload" "install" "microsoft-net-runtime-android" "--skip-manifest-update" "--verbosity" "diag"
	stderr | Workload with id microsoft-net-runtime-android is not recognized.

However, it was a bug in the `dotnet workload install` command that
allowed us to even install this workload in the first place!
The concept concept behind "abstract" workloads is they are not user
visible in any way; they're meant to be an implementation detail.

In commit 0150bbb, I setup `xaprepare` to install the
`microsoft-net-runtime-android` workload, but we don't actually even
need to do this.  We can simply update the `sdk-manifest` for this
pack, so that the version matches `$(DotNetRuntimePacksVersion)`.

The `microsoft-net-runtime-android` workload will get installed later
during the `ExtractWorkloadPacks` target, as part of installing the
`android` or `android-aot` workloads:

https://github.com/xamarin/xamarin-android/blob/c1a2ee70214e86757541b5759c9ed54941bd4680/build-tools/create-packs/Directory.Build.targets#L119-L122

Since `android` and `android-aot` extend
`microsoft-net-runtime-android`, this step will install it.
jonpryor pushed a commit that referenced this pull request Aug 26, 2021
Context: #6112 (review)

The .NET Preview 7 bump is failing with:

	Running: /Users/builder/Library/Android/dotnet/dotnet "workload" "install" "microsoft-net-runtime-android" "--skip-manifest-update" "--verbosity" "diag"
	stderr | Workload with id microsoft-net-runtime-android is not recognized.

However, it was a bug in the `dotnet workload install` command that
allowed us to even install this workload in the first place!
The concept concept behind "abstract" workloads is they are not user
visible in any way; they're meant to be an implementation detail.

In commit 0150bbb, I setup `xaprepare` to install the
`microsoft-net-runtime-android` workload, but we don't actually even
need to do this.  We can simply update the `sdk-manifest` for this
pack, so that the version matches `$(DotNetRuntimePacksVersion)`.

The `microsoft-net-runtime-android` workload will get installed later
during the `ExtractWorkloadPacks` target, as part of installing the
`android` or `android-aot` workloads:

https://github.com/xamarin/xamarin-android/blob/c1a2ee70214e86757541b5759c9ed54941bd4680/build-tools/create-packs/Directory.Build.targets#L119-L122

Since `android` and `android-aot` extend
`microsoft-net-runtime-android`, this step will install it.
@github-actions github-actions bot locked and limited conversation to collaborators Jan 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants