Read more

Deal with certain travis CI failures

Tobias Kraze
June 18, 2019Software engineer at makandra GmbH

Travis changed their default distribution from Ubuntu 14.04 (trusty) to 16.04 (precise). This might break your test setup for new builds.

Illustration online protection

Rails Long Term Support

Rails LTS provides security patches for old versions of Ruby on Rails (2.3, 3.2, 4.2 and 5.2)

  • Prevents you from data breaches and liability risks
  • Upgrade at your own pace
  • Works with modern Rubies
Read more Show archive.org snapshot

You can solve this issue by freezing your test distribution in the .travis.yml to Ubuntu 14.04 until you have the time to solve all the issues you will have in 16.04:


dist: trusty

Error details

Here are few indicators that you ran into this issue:

Connection to the PostgreSQL database does not work anymore

Your travis-ci builds might have started failing on the usual

psql -c 'create database active_type_test;' -U postgres

with an error

psql: could not connect to server: No such file or directory
	Is the server running locally and accepting
	connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?

Connection to the MySQL database does not work anymore

Your travis-ci builds might have started failing on the usual

mysql -e 'create database IF NOT EXISTS minidusen_test;'

with an error

ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
The command "mysql -e 'create database IF NOT EXISTS minidusen_test;'" failed and exited with 1 during .

Rails 2/3 migrations don't work anymore

bundle exec rspec spec
-- create_table(:users)
bundler: failed to load command: rspec (/home/travis/build/makandra/minidusen/vendor/bundle/ruby/2.2.0/bin/rspec)
ActiveRecord::StatementInvalid: Mysql2::Error: All parts of a PRIMARY KEY must be NOT NULL; if you need NULL in a key, use UNIQUE instead: CREATE TABLE `users` (`id` int(11) DEFAULT NULL auto_increment PRIMARY KEY, `name` varchar(255), `email` varchar(255), `city` varchar(255)) ENGINE=InnoDB


Posted by Tobias Kraze to makandra dev (2019-06-18 10:40)