Am Mon, 22 Jun 2015 20:37:40 +0200 schrieb "Iain Buclaw via D.gnu" <d.gnu@puremagic.com>:
> On 22 June 2015 at 19:58, Johannes Pfau via D.gnu > <d.gnu@puremagic.com> wrote: > > Am Mon, 22 Jun 2015 08:56:53 +0000 > > schrieb "Iain Buclaw" <ibuc...@gdcproject.org>: > > > >> As the autotester seems to be broken indefinitely for the time > >> being, I've been playing around with Travis for builds. > >> > >> https://travis-ci.org/ibuclaw/GDC/branches > >> > >> A couple of show stoppers I've been running into: > >> - Time to build, run testsuite, run unittests exceeds quota (50 > >> minutes) > >> - Memory consumption exceeds quota (claims to be a hard 3GB) > >> > >> This is interesting, to speed up builds it might be considered > >> logical to increase the number of parallel jobs, infact this > >> conflicts directly with the memory consumption quota, meaning > >> that the build needs to be carefully split up to run at different > >> parallel levels depending on the memory used. > >> > >> What seems to be a total blocker is that I seem to be getting > >> inconsistent results (in relation to out-of-memory errors) > >> depending on which host the build is running on. > > > > Maybe drop them a mail if they would consider upgrading the quotas > > for GDC. Regarding inconsistent results: If it's related to the > > build environment using docker might help? > > > > I suspect that would require money. https://travis-ci.com/plans > > (Their production build servers allow up to 2 hours) I don't know. It sounds like these plans are meant for commercial users. They probably only have limits for OSS projects to avoid abuse (like running a bitcoin miner or something) so I could imagine they might lift the limits on a case-by-case basis. OTOH if Semaphore works fine that's even better!
