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.

Sign up for GitHub

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

Jump to bottom

tracing issue - android CI #2514

Closed
2 tasks done
mockersf opened this issue Jul 21, 2021 · 0 comments
Closed
2 tasks done

tracing issue - android CI #2514

mockersf opened this issue Jul 21, 2021 · 0 comments
Labels
A-Build-System Related to build systems or continuous integration C-Tracking-Issue An issue that collects information about a broad development initiative

Comments

@mockersf
Copy link
Member

mockersf commented Jul 21, 2021 •
edited
Loading

Android CI check by Bors has been disabled in #2513 as it is failing without a simple path to fix.

This means that android CI jobs will continue to fail for all PRs/commits, but it won't block merges by Bors.

https://github.com/bevyengine/bevy/runs/3128035561:

Run cargo apk build --example android
  cargo apk build --example android
  shell: /usr/bin/bash -e {0}
  env:
    CARGO_TERM_COLOR: always
Warning: You use environment variable ANDROID_HOME that is deprecated. Please, remove it and use ANDROID_SDK_ROOT instead. Now ANDROID_HOME is used
Error: Path `"/usr/local/lib/android/sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/aarch64-linux-android31-clang"` doesn't exist.
Error: Process completed with exit code 1.

To Do

  • fix android CI job
  • re-enable check by Bors
@mockersf mockersf added A-Build-System Related to build systems or continuous integration C-Tracking-Issue An issue that collects information about a broad development initiative labels Jul 21, 2021
@mockersf mockersf mentioned this issue Jul 24, 2021
Closed
bors bot pushed a commit that referenced this issue Jul 26, 2021
@mockersf
Android uninstall 31 (#2533)
5583f9a 
# Objective

- Related to #2514 - not sure if it's a proper fix long term
- CI was complaining Error: Path `"/usr/local/lib/android/sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/aarch64-linux-android31-clang"` was not found
- A lot of questions started popping up 10 days ago about ["android build tools 31 corrupted"](https://www.google.com/search?q=android+build+tools+31+corrupted)
  - https://stackoverflow.com/questions/68387270/android-studio-error-installed-build-tools-revision-31-0-0-is-corrupted
- Uninstalling `"build-tools;31.0.0"` doesn't seem to work, as it removes other components even though `"build-tools;30.0.3"` are available


## Solution

- Uninstalling `"platforms;android-31"` seems to do the trick and `cargo-apk` stops trying to target `...31`

Android is not my thing, this solution was found with a lot of trials and errors. I am not sure how long term it is, I don't know the release schedule of android build tools, or if we need to target this 31 thing. I just wanted to stop all those failed ci everywhere...
ostwilkens pushed a commit to ostwilkens/bevy that referenced this issue Jul 27, 2021
@mockersf @ostwilkens
Android uninstall 31 (bevyengine#2533)
a6d7e78 
# Objective

- Related to bevyengine#2514 - not sure if it's a proper fix long term
- CI was complaining Error: Path `"/usr/local/lib/android/sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/aarch64-linux-android31-clang"` was not found
- A lot of questions started popping up 10 days ago about ["android build tools 31 corrupted"](https://www.google.com/search?q=android+build+tools+31+corrupted)
  - https://stackoverflow.com/questions/68387270/android-studio-error-installed-build-tools-revision-31-0-0-is-corrupted
- Uninstalling `"build-tools;31.0.0"` doesn't seem to work, as it removes other components even though `"build-tools;30.0.3"` are available


## Solution

- Uninstalling `"platforms;android-31"` seems to do the trick and `cargo-apk` stops trying to target `...31`

Android is not my thing, this solution was found with a lot of trials and errors. I am not sure how long term it is, I don't know the release schedule of android build tools, or if we need to target this 31 thing. I just wanted to stop all those failed ci everywhere...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-Build-System Related to build systems or continuous integration C-Tracking-Issue An issue that collects information about a broad development initiative
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mockersf