I agree something is affecting many of the Py3 PR builds but we can't see the errors because the logs are too verbose. I have a PR to limit log verbosity on Travis (except for failed tests) but it needs a +1, once that's in we should regain transparency in to the errors: https://github.com/apache/incubator-airflow/pull/2049
On Wed, Feb 8, 2017 at 7:37 AM Bolke de Bruin <[email protected]> wrote: I have noticed this as well and I do actually think it is something that has “ran” away. The ones that fail go on for much longer and are tied to python 3. Can someone have a look at its please? I am a bit preoccupied with getting the release out. Cheers Bolke > On 8 Feb 2017, at 13:18, Miller, Robin < [email protected]> wrote: > > Hi All, > > > On a couple of my open PRs, I've been having trouble getting the units tests to run successfully, not because there's a test failure, but because Travis is reporting that the unit test log has become too large: > > > " > > The log length has exceeded the limit of 4 MB (this usually means that the test suite is raising the same exception over and over). > > The job has been terminated > > " > > I've taken a look through the log and there's nothing obviously stuck in a loop; there are tests starting and passing pretty much to the bottom of the file. > > > Has something changed that means that the tests generate much more output? Or have we just reached a tipping point where we have too many tests for TravisCI to handle? For whatever reason this seems to be mainly happening for Python3 with MySQL or Postgres as the backend (see here for examples: https://travis-ci.org/apache/incubator-airflow/builds/199160045) > > > I don't believe this is caused by the tests I've added, as I don't believe it's even reached them in this run: https://api.travis-ci.org/jobs/199160051/log.txt?deansi=true > > > I appreciate any input on this, > > Robin Miller > OLIVER WYMAN > [email protected]<mailto: [email protected]> > www.oliverwyman.com<http://www.oliverwyman.com/> > > > ________________________________ > This e-mail and any attachments may be confidential or legally privileged. If you received this message in error or are not the intended recipient, you should destroy the e-mail message and any attachments or copies, and you are prohibited from retaining, distributing, disclosing or using any information contained herein. Please inform us of the erroneous delivery by return e-mail. Thank you for your cooperation.
