-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[Good First Issue]: Introduce testing on Android in GitHub Actions #26991
Comments
.take |
Thank you for looking into this issue! Please let us know if you have any questions or require any help. |
.take |
Thanks for being interested in this issue. It looks like this ticket is already assigned to a contributor. Please communicate with the assigned contributor to confirm the status of the issue. |
hey!, @geeky33 !! you still working on it? what's the status of your work? |
hi @darksapien23151 due to some health issues going on from 1-2 days i have just took a small break.. i will be back from tomorrow there are some errors occurring hence fixing those at the same time. |
Context
At the moment, we have two GitHub Actions workflows in which we cross-compile OpenVINO artefacts using Ubuntu 22 for Android x64 and arm64.
We would like to enable testing of the produced artefacts on an Android emulator in GitHub Actions.
What needs to be done?
The idea is to implement test jobs similarly to existing test jobs in other workflows:
ENABLE_TESTS=ON
in the cmake configuration step:openvino/.github/workflows/android_x64.yml
Line 124 in 3f70084
Many Android emulators are available:
In OpenVINO, we use pre-built Docker images for building and testing so it is recommended that you use a Docker image with an Android emulator for testing.
Refer to the OpenVINO GitHub Actions documentation for more details on the GitHub Actions setup.
Example Pull Requests
No response
Resources
Contact points
If you have any questions, please contact @akashchi and @mryzhov.
If you create a Pull Request, please add @akashchi and @mryzhov as reviewers and assignees.
Ticket
149906
The text was updated successfully, but these errors were encountered: