Travis Precise and gradle issues - please help!

[mbernier]

Issue Summary

As soon as Hacktoberfest started, we started getting failures from Travis. Are you familiar with this issue and able to help? There's some SendGrid Hacktoberfest swag in it for you :)

We are getting this issue:

This job ran on our Precise environment, which is in the process of being decommissioned. Please read about the status of the rollout on the blog, and take note that you can explicitly stay on Precise by specifying dist: precise in your .travis.yml.

and

The command "./gradlew check" exited with 134.

From travis.

Steps to Reproduce

1. See every PR on this repo right now :(

[aaomidi]

This issue depends on your use case, do you definitely need oraclejdk7? If not can it just be replaced with openjdk7?

[LulaV14]

I'm not sure that the problem is with the oraclejdk7...because there are three build jobs using openjdk7, oraclejdk7 and oraclejdk8 and all are failing in most of the builds.

I'm no expert in Travis but doing a little research I found that in most projects the problem was the permissions for the gradle file. I'm sure you did gave permissions because it wasn't failing.. maybe some PR change broke that?

What I would try is adding this:

before_install:
 - chmod +x gradlew

to the .travis.yml file to check if that fixes the problem.

[InfiniteCoder]

I can't locate the code that is pointed to in the errors of the log, as pointed by the travis beacon on readme page. It's pointing to build 451. Errors point to some import lines in Attachments.java, but those code lines do not exist in repository.

The only error that Attachments.java shows for me is that package name does not match the directory structure.

[LulaV14]

I see that @andy-trimble did some changes in the .travis.yml file and now all builds are passing 😊
So that was the problem? Everything's working now?

[andy-trimble]

This looks to be related to travis-ci/travis-ci#5227.

[mbernier]

#366 + @andy-trimble got the build running again!

[mbernier]

@andy-trimble I am curious if you think that running the entire build inside a docker container would solve the issue we talked about? https://docs.travis-ci.com/user/docker/

[andy-trimble]

I believe it would fix several things. We could also start up Prism as a container and avoid all the downloading, scripting, and sleeping. @mbernier