MySQL issues causing failure

[andrerom]

In the following build mysql (63.4) is failing but it is passing on travis and locally: shippable: https://app.shippable.com/builds/543d8663cc6c971400a4ec15 travis: https://travis-ci.org/ezsystems/ezpublish-kernel/builds/37979011

Side note: the shippable interface crashes tab in chrome when trying to expand the script output, only way to see it is downloading the 8mb log.

[manishas]

@andrerom we'll take a look and figure out what's going on. thanks for reporting this!

[andrerom]

Thanks, here is the .travis.yml file on public url btw with exact same sha1 as jobs above: https://github.com/ezsystems/ezpublish-kernel/blob/b03edea551cb579cebcfe14e5d0b9176958db398/.travis.yml

mysql relevant code:

    - TEST_CONFIG="phpunit-integration-legacy.xml" DB="mysql" DATABASE="mysql://root@localhost/$DB_NAME" SYMFONY_VERSION="2.3.*"

(...)

 - if [ $DB == "mysql" ]; then mysql -e "CREATE DATABASE IF NOT EXISTS $DB_NAME;" -uroot ; fi

So it uses database name mysql, and user root without password.

[rageshkrishna]

@andrerom We've discovered some issues around the order in which we export the environment variables. This seems to be what is causing your builds to break. We're working on a fix for this now and I'll update this issue as soon as it's available.

[rageshkrishna]

@andrerom We've rolled out a bunch of fixes for this. Your build should now run without issues, but there's a catch. Because of the way we manage our composer installation, our minions already have a ~/.composer directory so your ./composer_install_github_key.sh needs a minor modification. Instead of mkdir ~/.composer you should do mkdir -p ~/.composer. This should get everything to work.

Please let me know if this works for you.

[andrerom]

Hi, yes it seems to work, thanks! Only issue remaining on our side seems to be PHP 5.3.3, however that is covered by other issue so closing this one.