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

Investigate why the TravisCI build fails regularly [DATACASS-381] #511

Closed
spring-projects-issues opened this issue Jan 3, 2017 · 1 comment
Assignees
Labels
type: task A general task
Milestone

Comments

@spring-projects-issues
Copy link

Mark Paluch opened DATACASS-381 and commented

TravisCI builds fail rather often (each build is unsuccessful). Individual build jobs behave inconsistently regarding their success/failure rate and the reason is not obvious why builds fail. Build failures occur during integration testing, the driver reports timeouts, no available nodes and faulty responses on arbitrary jobs without a consistent pattern


Affects: 1.5 RC1 (Ingalls), 2.0 M1 (Kay)

Referenced from: commits 7563e9b, efba60b

Backported to: 1.5 GA (Ingalls)

@spring-projects-issues
Copy link
Author

Mark Paluch commented

Reuse Thread pools during integration test runs to not recreate and dispose Threads multiple times. Increase build and Cassandra memory. Use an external Cassandra instance for TravisCI build jobs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: task A general task
Projects
None yet
Development

No branches or pull requests

2 participants