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
Setup Travis CI to run our test suite on each pull request automatically #3722
Comments
Previous builds failed due to a missing config.ini.php. [7833] (forgot the refs) |
(In [7836]) Syntax error in .travis.yml refs #3722 |
(In [7838]) Make travis.sh executable refs #3722 |
The PHP 5.5 build is currently throwing a ton of E_DEPRECATED warnings since they are using an outdated version of PHPUnit. I created a ticket in their issue tracker: travis-ci/travis-ci#903 |
In f2bd670: Fixed the issue with vagrant & failing tests. The solution is to setup webserver to Piwik.
|
https://travis-ci.org/piwik/piwik/jobs/4658397
I'm splitting up test suites again. Not sure why the tests suddenly take so long to run as they were finished within less than 10 minutes before. |
I'm pretty sure I had this problem before. Usually, it completely crashes either the computer (swapping) or php/phpunit. One problem comes when generating & displaying the backtrace for the test failures. Some backtrace are just too huge to be displayed, and result in crash or minutes of waiting. I think this is the problem here. I think that, once all tests pass again, this can be switched back to "full build" to try again. |
It would be nice if we could enable build on both PDO Mysql and Mysqli |
Is it possible to setup Mysqli on Travis ? Otherwise this ticket can be closed I think. excellent work! |
Should be possible - still on my list. |
what a nice tool! it will tremendously help, especially if Jenkins crashes or dies in the future. Kuddos!! |
Hey, sorry to answer a very old issue, but I have the same timeout problem. How did you fix it? Does every test matrix has it's own timeout? I cannot find any information on how to properly split test suites in travis.yml. |
Neither do I. Did you find some information @vvo? |
yes, use matrixes. timeout is per job in the matrix! |
Thanks! |
It would be awesome if the build was running automatically for all pull requests.
we would know, when reviewing a pull request, if the code is relatively safe.
Ideally Travis would notify in the pull request page the build result, (and link contributors to the doc explaining how to run tests).
Started in [7826]
Non trivial Feature requests:
The text was updated successfully, but these errors were encountered: