Re: [Mixxx-devel] Travis CI False Positives Mac Builds

2016-11-15 Thread Be
On 11/15/2016 02:46 PM, Daniel Schürmann wrote: > It would be no issue for me if we skip most tests during the Mac build, > since most of them are target independent an already tested during the > Linux build. They should be, but disabling tests on one platform could get us into trouble down

Re: [Mixxx-devel] Travis CI False Positives Mac Builds

2016-11-15 Thread Daniel Schürmann
Hi RJ, > I think we could shorten that to 1 second and still get the desired effect. WDYT? IMHO the 30 s 1kHzR440HzLReference_32i96kStereo file is not used during automatic tests. It would be no issue for me if we skip most tests during the Mac build, since most of them are target

Re: [Mixxx-devel] Travis CI False Positives Mac Builds

2016-11-15 Thread RJ Ryan
Oh, apparently going over 4MB gets you killed. I'll turn off verbose compilation. On Tue, Nov 15, 2016 at 11:54 AM RJ Ryan wrote: > Hm, I got something slightly different on that commit. > https://api.travis-ci.org/jobs/176113186/log.txt?deansi=true > > "The log length has

Re: [Mixxx-devel] Travis CI False Positives Mac Builds

2016-11-15 Thread RJ Ryan
Hm, I got something slightly different on that commit. https://api.travis-ci.org/jobs/176113186/log.txt?deansi=true "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 can't tell if

[Mixxx-devel] Travis CI False Positives Mac Builds

2016-09-15 Thread Daniel Schürmann
Hi, we get lately a lot of false positives building Mixxx on Mac via Travis: https://travis-ci.org/mixxxdj/mixxx/builds/160026424 This is because Travis has a 45 min time out. Can one of the Mac contributors have a look at it? What is the easiest way to reduce the build time? Thank you,