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/9.0-staging] Re-enable skiasharp WBT tests (#109232) #110734

Open
wants to merge 1 commit into
base: release/9.0-staging
Choose a base branch
from

Conversation

radekdoulik
Copy link
Member

@radekdoulik radekdoulik commented Dec 16, 2024

Backport of #109232 to release/9.0-staging

Customer Impact

  • Customer reported
  • Found internally

The linker problem, which was found internally when re-enabling skiasharp tests. The problem was already resolved by the llvm update in #110409

Regression

  • Yes
  • No

Testing

This PR enables the relevant tests on CI, to confirm the llvm fix works fine on 9.0 branch.

Risk

Low risk, this PR enables CI tests only.

IMPORTANT: If this backport is for a servicing release, please verify that:

  • The PR target branch is release/X.0-staging, not release/X.0.

Package authoring no longer needed in .NET 9

IMPORTANT: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version.
Keep in mind that we still need package authoring in .NET 8 and older versions.

Resolves #103566

* [wasm] Re-enable skiasharp WBT tests

* Disable Debug/AOT combination

That would trigger build error, because we don't support that combination
anymore

* Change order of native libs

Put NativeFileReference files after the runtime libs. This server as
a workaround of dotnet#109289

* Update llvm, emsdk and icu deps

* Revert "Change order of native libs"

This reverts commit e320fd6.
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Dec 16, 2024
@radekdoulik radekdoulik added area-Infrastructure-mono and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Dec 16, 2024
@radekdoulik radekdoulik added this to the 9.0.x milestone Dec 16, 2024
Copy link
Contributor

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

Copy link
Member

@ilonatommy ilonatommy left a comment

Choose a reason for hiding this comment

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

Why is WASI down? Apart from that, approved.

Copy link
Member

@jeffschwMSFT jeffschwMSFT left a comment

Choose a reason for hiding this comment

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

approved. we can take this as tell mode. once ready this can be merged

@jeffschwMSFT jeffschwMSFT added the Servicing-approved Approved for servicing release label Jan 9, 2025
@jeffschwMSFT jeffschwMSFT modified the milestones: 9.0.x, 9.0.2 Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants