-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Upgrade Android platform images to a more recent version #120567
Comments
tmandry
added a commit
to tmandry/rust
that referenced
this issue
Feb 2, 2024
Until rust-lang#120567 is fixed.
tmandry
added a commit
to tmandry/rust
that referenced
this issue
Feb 2, 2024
Until rust-lang#120567 is fixed.
maurer
added a commit
to maurer/rust
that referenced
this issue
Feb 2, 2024
We were running testing on API 18, which was already out of support for NDK 25, and some of the ancient behavior in that image was causing trouble when developing `rustc` features (rust-lang#120326). We'll be updating to NDK 26 (latest LTS) shortly, so rather than updating to API 19, then again to API 21 in a bit, just jump straight to 21. Fixes: rust-lang#120567
maurer
added a commit
to maurer/rust
that referenced
this issue
Mar 24, 2024
We were running testing on API 18, which was already out of support for NDK 25, and some of the ancient behavior in that image was causing trouble when developing `rustc` features (rust-lang#120326). We'll be updating to NDK 26 (latest LTS) shortly, so rather than updating to API 19, then again to API 21 in a bit, just jump straight to 21. Fixes: rust-lang#120567
maurer
added a commit
to maurer/rust
that referenced
this issue
May 7, 2024
We were running testing on API 18, which was already out of support for NDK 25, and some of the ancient behavior in that image was causing trouble when developing `rustc` features (rust-lang#120326). Update to the current LTS NDK 26, and to its minimum supported API 21. Fixes: rust-lang#120567
maurer
added a commit
to maurer/rust
that referenced
this issue
May 18, 2024
We were running testing on API 18, which was already out of support for NDK 25, and some of the ancient behavior in that image was causing trouble when developing `rustc` features (rust-lang#120326). Update to the current LTS NDK 26, and to its minimum supported API 21. Fixes: rust-lang#120567
maurer
added a commit
to maurer/rust
that referenced
this issue
Jul 10, 2024
We were running testing on API 18, which was already out of support for NDK 25, and some of the ancient behavior in that image was causing trouble when developing `rustc` features (rust-lang#120326). Update to the current LTS NDK 26, and to its minimum supported API 21. Fixes: rust-lang#120567
maurer
added a commit
to maurer/rust
that referenced
this issue
Jul 18, 2024
We were running testing on API 18, which was already out of support for NDK 25, and some of the ancient behavior in that image was causing trouble when developing `rustc` features (rust-lang#120326). Update to the current LTS NDK 26, and to its minimum supported API 21. Fixes: rust-lang#120567
maurer
added a commit
to maurer/rust
that referenced
this issue
Jul 19, 2024
We were running testing on API 18, which was already out of support for NDK 25, and some of the ancient behavior in that image was causing trouble when developing `rustc` features (rust-lang#120326). Update to the current LTS NDK 26, and to its minimum supported API 21. Fixes: rust-lang#120567
maurer
added a commit
to maurer/rust
that referenced
this issue
Jul 25, 2024
We were running testing on API 18, which was already out of support for NDK 25, and some of the ancient behavior in that image was causing trouble when developing `rustc` features (rust-lang#120326). Update to the current LTS NDK 26, and to its minimum supported API 21. Fixes: rust-lang#120567
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently Rust CI uses an Android platform image with API level 18, which was released more than 10 years ago in 2013.
I first realized this when working on #120326 and noticing that aborts resulted in SIGSEGV, which libc used to do on Android up until sometime in 2013.
From talking with @maurer it sounds like the right thing to do is to upgrade the platform image to one with ABI level 25, now that it's the min supported NDK target.
This issue has been assigned to @maurer via this comment.
The text was updated successfully, but these errors were encountered: