Jenkins CI behaviour

classic Classic list List threaded Threaded
8 messages Options
Rahul Gurung Rahul Gurung
Reply | Threaded
Open this post in threaded view
|

Jenkins CI behaviour

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.

Thanks,
RG

_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
kara kara
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins CI behaviour

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 list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Best,
Muhammet
_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Rahul Gurung Rahul Gurung
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins CI behaviour

What if it hiccups again in rebase ?

On 27 August 2018 at 19:11, Muhammet Kara <[hidden email]> 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 list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Best,
Muhammet


_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Markus Mohrhard Markus Mohrhard
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins CI behaviour

Hey,

On Tue, Aug 28, 2018 at 5:52 PM Rahul Gurung <[hidden email]> 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 <[hidden email]> 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 list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Best,
Muhammet

_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice

_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Rahul Gurung Rahul Gurung
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins CI behaviour

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

On 28 August 2018 at 21:27, Markus Mohrhard <[hidden email]> wrote:
Hey,

On Tue, Aug 28, 2018 at 5:52 PM Rahul Gurung <[hidden email]> 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 <[hidden email]> 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 list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Best,
Muhammet

_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice


_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Markus Mohrhard Markus Mohrhard
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins CI behaviour

Hey,

On Tue, Aug 28, 2018 at 6:36 PM Rahul Gurung <[hidden email]> wrote:
How to do that, because rebasing twice doesn't seems possible?


You need at least one new commit on master, otherwise rebasing is not possible. So unless you try to rebase quickly after each other it should be possible.

Regards,
Markus

On 28 August 2018 at 21:27, Markus Mohrhard <[hidden email]> wrote:
Hey,

On Tue, Aug 28, 2018 at 5:52 PM Rahul Gurung <[hidden email]> 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 <[hidden email]> 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 list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Best,
Muhammet

_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice


_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Eike Rathke-2 Eike Rathke-2
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins CI behaviour

In reply to this post by Markus Mohrhard
Hi,

On Tuesday, 2018-08-28 17:57:23 +0200, Markus Mohrhard wrote:

> On Tue, Aug 28, 2018 at 5:52 PM Rahul Gurung <[hidden email]> 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.

This specific (JunitTest_framework_complex) test seemed to always fail on
(only?) tb75 building gerrit_linux_clang_dbgutil, for the last two days
or so; then for the last 14 hours looked stable; currently it seems
those builds get aborted by whoever/whatever. See
https://ci.libreoffice.org/computer/tb75-lilith/builds

So one is lucky if the gerrit_linux_clang_dbgutil build gets triggered
on a different machine.

  Eike

--
LibreOffice Calc developer. Number formatter stricken i18n transpositionizer.
GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918  630B 6A6C D5B7 6563 2D3A

_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice

signature.asc (849 bytes) Download Attachment
sberg sberg
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins CI behaviour

On 28/08/18 18:45, Eike Rathke wrote:
> This specific (JunitTest_framework_complex) test seemed to always fail on
> (only?) tb75 building gerrit_linux_clang_dbgutil, for the last two days
> or so; then for the last 14 hours looked stable; currently it seems
> those builds get aborted by whoever/whatever. See
> https://ci.libreoffice.org/computer/tb75-lilith/builds

JunitTest_framework_complex had failed there because stale processes
from a previous build were still hanging around, so ca. two days ago I
took tb75 temporarily offline, killed the leftover processes, and took
the tb back online.

At least the most recent build of "Gerrit Linux clang/dbgutil" on tb75,
<https://ci.libreoffice.org/job/gerrit_linux_clang_dbgutil/13849/> is
green again, so I assume the above actions were effective and
everything's back to fine again.
_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice