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

Bump SdkVersionForWorkloadTesting to use a 200 band SDK #63450

Merged
merged 3 commits into from
Jan 7, 2022

Conversation

steveisok
Copy link
Member

#62787 bumped the manifest id. This change bumps the prop for testing.

dotnet#62787 bumped the manifest id.  This change bumps the prop for testing.
@dotnet-issue-labeler
Copy link

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.

@ghost
Copy link

ghost commented Jan 6, 2022

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

#62787 bumped the manifest id. This change bumps the prop for testing.

Author: steveisok
Assignees: steveisok
Labels:

area-Infrastructure

Milestone: -

Instead of trying to use the script from `.dotnet`, download the script.
`.dotnet` might not exist, for example, when the `global.json` version
matches the system installed one.
To resolve a workload, the current version band is used to look in
`sdk-manifests` directory. But when in development, and bumping to a
newer version band, not all the manifests might have packages for that.

This shows up when bumping the band to `6.0.200`, where we generate
the corresponding packages for wasm-tools. But the Emscripten packages
are still on `6.0.100`.

SDK [added](dotnet/sdk#19545) support for
falling back to older bands in that case.

The `InstallWorkloadFromArtifacts` task emits a warning about not being
able to find the emscripten manifest package. But this becomes an error
on CI due to warnaserror=true.

So, log a message instead of a warning. But this is only done for the
*dependent* manifest.
@steveisok
Copy link
Member Author

Failures are unrelated (networking)

@safern safern merged commit a66e67b into dotnet:release/6.0-maui Jan 7, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Feb 6, 2022
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.

6 participants