Hi Max,

The CI builds are still being worked on, very much an Alpha state right now.

Do you need the code reviewed regardless or do you want to wait for the CI builds to be fixed?

Best Regards, Martin Owens

On Sun, 2017-06-11 at 21:58 +0200, Maximilian Gaukler wrote:

Hi,

as I saw you are migrating to gitlab, I wanted to submit a merge request  for a patch I already proposed on launchpad. Unfortunately, the build  takes way longer than the 1 hour timeout and therefore all my commits  are flagged as "build failed": https://gitlab.com/mgmax/inkscape/builds/18388005

The first run made it to 77%, the second run to 39% of the build :-(

Greetings,

Max

---

---

Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

On 06/11/2017 02:58 PM, Maximilian Gaukler wrote:

as I saw you are migrating to gitlab, I wanted to submit a merge request for a patch I already proposed on launchpad. Unfortunately, the build takes way longer than the 1 hour timeout and therefore all my commits are flagged as "build failed": https://gitlab.com/mgmax/inkscape/builds/18388005

Unfortunately this setting is in your individual repository, so we can't adjust it there. I've updated the one in the Inkscape repository to be 180m, but I think if you forked before I set that yours will be set to the default 60m. Generally speaking we have normal builds down below that if you have the ccache warm already, they only take that long if there is no cache.

Ted