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/8.0-staging] Change assembler to clang in android MonoAOT #111666

Merged

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jan 21, 2025

Backport of #110393 to release/8.0-staging

/cc @jkurdek

Customer Impact

  • Customer reported
  • Found internally

The PR backports all the necessary bits for bumping the NDK version to 27. The currently used version (23) is significantly out of date and is not a supported version by Android. We have already bumped the version of the NDK used on .net10 and .net 9 branches.

Description of backported changes

Regression

  • Yes
  • No

Testing

https://github.com/dotnet/runtime/pull/112480/files
This PR references images with NDK 27. Failures on android lanes are unrelated to the changes in this PR.

Risk

Medium

  • Android NDK 27 uses clang 17. On .net 8 branch we use clang 16. This haven't caused any issues on the CI but some changes in behaviour could have slipped our tests.

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.

…, libClang.so is no longer found in the place we expect. As a result, the android aot offsets won't be generated and the dedicated CI leg will fail.

This change fixes the path.
@jkurdek jkurdek force-pushed the backport/pr-110393-to-release/8.0-staging branch from 8c4219f to 64286d4 Compare January 22, 2025 14:42
@jkurdek jkurdek self-assigned this Jan 22, 2025
@jkurdek
Copy link
Member

jkurdek commented Jan 22, 2025

/azp run runtime-extra-platforms

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@jkurdek
Copy link
Member

jkurdek commented Feb 4, 2025

/azp run runtime-extra-platforms

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@jkurdek jkurdek requested review from steveisok, jeffschwMSFT, ivanpovazan and vitek-karas and removed request for SamMonoRT and Copilot February 13, 2025 14:56
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.

lgtm. please get a code review. we will take for consideration in 8.0.x

@jeffschwMSFT jeffschwMSFT added the Servicing-consider Issue for next servicing release review label Feb 13, 2025
@jeffschwMSFT jeffschwMSFT added this to the 8.0.x milestone Feb 13, 2025
@jkurdek jkurdek requested a review from kotlarmilos February 17, 2025 15:50
Copy link
Member

@ivanpovazan ivanpovazan left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

Just please make sure we did not introduce any regression on runtime-extra-platforms pipeline.

@rbhanda rbhanda modified the milestones: 8.0.x, 8.0.15 Feb 20, 2025
@rbhanda rbhanda added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Feb 20, 2025
@jeffschwMSFT
Copy link
Member

@jkurdek please take a look at the PR failures. we can merge when ready

@jkurdek
Copy link
Member

jkurdek commented Mar 3, 2025

/azp run runtime-extra-platforms

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@jkurdek
Copy link
Member

jkurdek commented Mar 5, 2025

/ba-g the failures are unrelated. Cryptography tests are a known failure

@jkurdek
Copy link
Member

jkurdek commented Mar 10, 2025

/ba-g the failures are not on Android. unrelated.

@jkurdek
Copy link
Member

jkurdek commented Mar 10, 2025

@jeffschwMSFT the failures are unrelated. I cant click the merge button for some reason.

@jeffschwMSFT jeffschwMSFT merged commit 7ea3ab4 into release/8.0-staging Mar 10, 2025
7 of 22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Build-mono Servicing-approved Approved for servicing release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants