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
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
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)
The text was updated successfully, but these errors were encountered: