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

Travis fix for emulator build failures #116

Merged
merged 1 commit into from Jun 30, 2019

Conversation

Projects
None yet
2 participants
@jddeep
Copy link
Contributor

commented Jun 9, 2019

Fixes #115
Travis fix for emulator build failures.

@jddeep jddeep force-pushed the jddeep:travis-fix branch 9 times, most recently from f5223c9 to ef8aff2 Jun 9, 2019

@jddeep

This comment has been minimized.

Copy link
Contributor Author

commented Jun 10, 2019

@championswimmer @aggarwalpulkit596 Currently the error is : Unable to detect adb version, adb output: /usr/local/android-sdk/platform-tools/adb: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.16' not found (required by /usr/local/android-sdk/platform-tools/adb)` . I have tried many changes in the .yml file, changes locally but this particular error log seems not to get fixed. Any ideas?

@jddeep jddeep force-pushed the jddeep:travis-fix branch 3 times, most recently from e2ae7cb to b3952b5 Jun 11, 2019

@jddeep

This comment has been minimized.

Copy link
Contributor Author

commented Jun 12, 2019

@championswimmer @aggarwalpulkit596 Currently the error is : Unable to detect adb version, adb output: /usr/local/android-sdk/platform-tools/adb: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.16' not found (required by /usr/local/android-sdk/platform-tools/adb)` . I have tried many changes in the .yml file, changes locally but this particular error log seems not to get fixed. Any ideas?

@aggarwalpulkit596 I HAVE FIXED THE EMULATOR ERROR but I have been working for days trying to resolve this error. The builds run fine and have been successful here locally.

@jddeep

This comment has been minimized.

Copy link
Contributor Author

commented Jun 12, 2019

@aggarwalpulkit596 The jacocoTestReport gives errors like No view with id xyz was found in the view hierarchy but I looked through the layouts and it's bindings, everything was fine and even the layouts got created in the app perfectly. Why do you think this is happening?

@aggarwalpulkit596

This comment has been minimized.

Copy link
Contributor

commented Jun 12, 2019

You have changed the layouts so you have to the change it in instrumentation test as well

@jddeep

This comment has been minimized.

Copy link
Contributor Author

commented Jun 12, 2019

@aggarwalpulkit596 First of all the layout which I changed, was in a different branch. Here in this branch everything is same. Moreover, the test failures are of different layouts.

@jddeep

This comment has been minimized.

Copy link
Contributor Author

commented Jun 12, 2019

@aggarwalpulkit596 I have checked the layouts thoroughly, they are completely fine with correct ids. We can do one thing. I have fixed the emulator test fails and ./gradlew build fails. You can merge this and see the latter error yourself once.

@jddeep

This comment has been minimized.

Copy link
Contributor Author

commented Jun 12, 2019

@championswimmer @aggarwalpulkit596 There were also some errors of validatesigning. I took care of those as well, as you can see from the files changed. Thanks.

@aggarwalpulkit596

This comment has been minimized.

Copy link
Contributor

commented Jun 13, 2019

The exception which Travis is showing is that
com.android.builder.testing.api.DeviceException: Could not create ADB Bridge. ADB location: /usr/local/android-sdk/platform-tools/adb
you need to fix that first

@jddeep

This comment has been minimized.

Copy link
Contributor Author

commented Jun 13, 2019

The exception which Travis is showing is that
com.android.builder.testing.api.DeviceException: Could not create ADB Bridge. ADB location: /usr/local/android-sdk/platform-tools/adb
you need to fix that first

There is no such issue for adb when I run the jacocoTestReport locally. I think the project's travis needs to be changed completely, need to remove lot of things. Cause otherwise this adb issue persists over here, have tried every possible solution I could find.

@aggarwalpulkit596

This comment has been minimized.

Copy link
Contributor

commented Jun 13, 2019

JacocoTestReport is an different thing and not at all connected to Travis read about Travis on their website

@jddeep

This comment has been minimized.

Copy link
Contributor Author

commented Jun 13, 2019

JacocoTestReport is an different thing and not at all connected to Travis read about Travis on their website

But in the Travis build log here, the command for which the test is failing is jacocoTestReport.

@jddeep

This comment has been minimized.

Copy link
Contributor Author

commented Jun 13, 2019

So naturally i need to test that command locally. But that command does not gives any adb error locally. Instead gives some missing layout ids stuff which i haven't changed anything.

@jddeep

This comment has been minimized.

Copy link
Contributor Author

commented Jun 13, 2019

@aggarwalpulkit596 Did you get what i am saying?

@jddeep jddeep force-pushed the jddeep:travis-fix branch from da87748 to 37df92d Jun 13, 2019

@aggarwalpulkit596

This comment has been minimized.

Copy link
Contributor

commented Jun 13, 2019

The point is that there is nothing wrong JacocoTestReport but the tools and emulator which Travis build for generating report are obsolete and needs to be updated

@jddeep

This comment has been minimized.

Copy link
Contributor Author

commented Jun 13, 2019

The point is that there is nothing wrong JacocoTestReport but the tools and emulator which Travis build for generating report are obsolete and needs to be updated

I am trying different ways and will keep on trying. One thing, so do I need to simply update the $BUILD_TOOLS?

@jddeep jddeep force-pushed the jddeep:travis-fix branch from 37df92d to 56aaf1c Jun 30, 2019

@jddeep jddeep force-pushed the jddeep:travis-fix branch from 56aaf1c to badb4c8 Jun 30, 2019

@jddeep

This comment has been minimized.

Copy link
Contributor Author

commented Jun 30, 2019

@aggarwalpulkit596 @championswimmer Have fixed the error mentioned for Issue #116 . Now it is upto you guys (admins) to care of this :
Execution failed for task ':app:validateSigningRelease'. Keystore file not set for signing config release

@jddeep jddeep force-pushed the jddeep:travis-fix branch 7 times, most recently from 8e12ea3 to 5f22593 Jun 30, 2019

@jddeep jddeep force-pushed the jddeep:travis-fix branch from 5f22593 to c706214 Jun 30, 2019

@jddeep

This comment has been minimized.

Copy link
Contributor Author

commented Jun 30, 2019

@aggarwalpulkit596 Please merge this ASAP so that I can proceed with further issues.

@aggarwalpulkit596 aggarwalpulkit596 merged commit 434b415 into coding-blocks:master Jun 30, 2019

4 checks passed

ci/circleci Your tests passed on CircleCI!
Details
codebeat no reportable quality changes
Details
codeclimate All good!
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
@jddeep

This comment has been minimized.

Copy link
Contributor Author

commented Jul 1, 2019

@aggarwalpulkit596 I have claimed the bounty for this and some others. Please accept them. Thanks.

aggarwalpulkit596 added a commit that referenced this pull request Jul 6, 2019

Revert "travis-fix (#116)"
This reverts commit 434b415.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.