Working Android emulator based tests not working anymore

Build Environment Mobile
1

The same test was passing till yesterday and is failing now.
https://circleci.com/gh/ashishb/adb-enhanced/350?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link

#!/bin/bash -eo pipefail export LD_LIBRARY_PATH={ANDROID_HOME}/emulator/lib64:{ANDROID_HOME}/emulator/lib64/qt/lib && emulator64-arm -avd test -noaudio -no-boot-anim -no-window -accel on

EglOsGlLibrary: Could not open GL library libGLESv2.so [libGLESv2.so: cannot open shared object file: No such file or directory] EglOsEglDispatcher: Could not open EGL library libEGL.so [libEGL.so: cannot open shared object file: No such file or directory] Received ‘segmentation fault’ signal

1 Like
2

There’s two things that have changed:

  • You made a commit, after which things did not work
  • Your circleci/android hash has changed

You could try pinning to the last working hash (circleci/android@sha256:5cdc8626cc6f13efe5ed982cdcdb432b0472f8740fed8743a6461e025ad6cdfc) and then seeing if your new config works. If not, try rolling back to the last working commit - it looked like your work was very stable, and then has had two days of instability.

3

6 days back https://circleci.com/workflow-run/02bfba17-38f9-4404-b88e-58228014a504 succeeded. I re-ran that - https://circleci.com/gh/ashishb/adb-enhanced/358

it failed with

#!/bin/bash -eo pipefail
export LD_LIBRARY_PATH=${ANDROID_HOME}/emulator/lib64:${ANDROID_HOME}/emulator/lib64/qt/lib && emulator64-arm -avd test -noaudio -no-boot-anim -no-window -accel on
EglOsGlLibrary: Could not open GL library libGLESv2.so [libGLESv2.so: cannot open shared object file: No such file or directory]
EglOsEglDispatcher: Could not open EGL library libEGL.so [libEGL.so: cannot open shared object file: No such file or directory]
Received 'segmentation fault' signal```
4

Actually, am facing the same problem @ashishb, did you manage to solve it? Circle CI should elaborate on this please?

5

No, last I checked it is still broken for me. Fortunately, I have Travis CI setup as well which is slow but works.

6

This is actually a known issue with a security patch to the latest official java image (which I believe your image is based on). https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925

Moving to an older SHA is a good troubleshooting step.
Could you try to use sha?

circleci/android@sha256:5cdc8626cc6f13efe5ed982cdcdb432b0472f8740fed8743a6461e025ad6cdfc
1 Like
7

Thanks. this worked.

8

@ashishb, could you please explain the SHA, am kinda lost .

9

That’s how I pinned - https://github.com/ashishb/adb-enhanced/commit/7d382e06a67ed109506124cac5fd8c566bbf9210

1 Like
10

That’s great, but I posted the same solution some five days earlier! :roll_eyes:

11

I wonder, what I know is that every device has its own content required.my be you installed emulator that is not recognized by binaries to help su drive rar and tar into root access.Many market store provide running and prank items so long us they can run on Android it doesn’t matter which version those softwares cause device go crazy.better to install unmatured zip and extract it yourself for installation.:calling::closed_book::unlock::joy:

12

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.