Re: Jenkins CI behaviour

How to do that, because rebasing twice doesn't seems possible?

On 28 August 2018 at 21:27, Markus Mohrhard <markus.mohrhard@googlemail.com>
wrote:

> Hey,
>
> On Tue, Aug 28, 2018 at 5:52 PM Rahul Gurung <gurungrahul2@gmail.com>
> wrote:
>
> > What if it hiccups again in rebase ?
>
>
> Rebase again. Sadly some of the tests are not as stable as they should be.
> Some of the old java tests and some of the platform dependent tests (either
> font based, or other platform parts) fail from time to time.
>
> Just make sure that you are not causing the test failure before rebasing.
>
> Regards,
> Markus
>
>
> > On 27 August 2018 at 19:11, Muhammet Kara <muhammet.kara@pardus.org.tr>
> > wrote:
> >
> > > Hi Rahul,
> > >
> > > On 08/27/2018 01:58 PM, Rahul Gurung wrote:
> > >
> > > hey,
> > >
> > > Why do we get that "junit test JunitTest_framework_complex failed"
> > > message when we upload a patch and weird thing is it gets fixed by a
> > > rebase? which rebase is recommended, normal or ticking that option we get ?
> > > sorry im a newbie.
> > >
> > >
> > > It is not something standard. Our Jenkins sometimes hiccups, which
> > > causes such failures; and a rebase usually solves the issue for you by
> > > triggering another build (with the latest commits).
> > >
> > > Thanks,
> > > RG
> > >
> > >
> > > _______________________________________________
> > > LibreOffice mailing 
> > > listLibreOffice@lists.freedesktop.orghttps://lists.freedesktop.org/mailman/listinfo/libreoffice
> > >
> > >
> > > Best,
> > > Muhammet
> >
> > _______________________________________________
> > LibreOffice mailing list
> > LibreOffice@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/libreoffice