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

Android: No toolchains found in the NDK toolchains folder for ABI with prefix: arm-linux-androideabi #3561

Closed
Vayth opened this issue Oct 7, 2021 · 1 comment
Assignees

Comments

@Vayth
Copy link

Vayth commented Oct 7, 2021

I got and error when building Android project with error No toolchains found in the NDK toolchains folder for ABI with prefix: arm-linux-androideabi. However, the error first appeared on agent version 2.193.0 / image version 20210929.1. The same code built fine with agent version 2.192.0 / image version 20210919.1 and also built fine on local machine. That made me think that the issue lies in something that changed in that version.

Initialize Job Task - Success:

Starting: Initialize job
Agent name: 'Hosted Agent'
Agent machine name: 'fv-az394-23'
Current agent version: '2.192.0'
Operating System
Virtual Environment
Virtual Environment Provisioner
Current image version: '20210919.1'
Agent running as: 'vsts'
Prepare build directory.

Initialize Job Task - Failed:

Starting: Initialize job
Agent name: 'Hosted Agent'
Agent machine name: 'fv-az216-247'
Current agent version: '2.193.0'
Operating System
Virtual Environment
Virtual Environment Provisioner
Current image version: '20210929.1'
Agent running as: 'vsts'
Prepare build directory.

The solutions I found on the net seems to be upgrading/downgrading NDK version, but since this is a hosted-agent, I'm not sure how to do that, nor I know what version/changes in the image.

Any advice or solution to this?

note: I also posted this on StackOverflow which may contains slightly more information

@DaniilShmelev
Copy link
Contributor

Hi @Vayth! This looks like a problem with an image and not the agent. And there's also a similar issue already opened in their repo: actions/runner-images#4225
Closing this for now, feel free to ping me if you have any questions!

DmitriiBobreshev added a commit to DmitriiBobreshev/azure-pipelines-agent that referenced this issue Oct 14, 2022
…ell script for add VM resource in New Environment in ADO Server microsoft#3561

- Moved part of the logic from the ConfigureAsync to other functions in ConfigurationManager.cs
- Added flag IsCollectionPossible in IConfigurationProvider
- Added some logic to prevent exception when defaultCollection is possible
DmitriiBobreshev added a commit to DmitriiBobreshev/azure-pipelines-agent that referenced this issue Oct 19, 2022
…ell script for add VM resource in New Environment in ADO Server microsoft#3561

- Added some methods to interfaces
- Removed cast from configManager.cs
DmitriiBobreshev added a commit that referenced this issue Nov 2, 2022
…ell script for add VM resource in New Environment in ADO Server #3561 (#3992)

* [Bug 1942506](P2): [Pipelines]: PAT invalid in auto-generated PowerShell script for add VM resource in New Environment in ADO Server #3561

- Moved part of the logic from the ConfigureAsync to other functions in ConfigurationManager.cs
- Added flag IsCollectionPossible in IConfigurationProvider
- Added some logic to prevent exception when defaultCollection is possible

* [Bug 1942506](P2): [Pipelines]: PAT invalid in auto-generated PowerShell script for add VM resource in New Environment in ADO Server #3561

- Added some methods to interfaces
- Removed cast from configManager.cs

Co-authored-by: Kirill Ivlev <102740624+kirill-ivlev@users.noreply.github.com>
Co-authored-by: Maxim Zaytsev <v-mazayt@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants