Re: Jenkins CI behaviour

Stephan Bergmann <sbergman -AT- redhat.com>
Wed, 29 Aug 2018 10:53:59 +0200

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 processesfrom a previous build were still hanging around, so ca. two days ago Itook tb75 temporarily offline, killed the leftover processes, and tookthe 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/> isgreen again, so I assume the above actions were effective andeverything's back to fine again.

Context

Jenkins CI behaviour · Rahul Gurung
- Re: Jenkins CI behaviour · Muhammet Kara
  - Re: Jenkins CI behaviour · Rahul Gurung
    - Re: Jenkins CI behaviour · Markus Mohrhard
      - Re: Jenkins CI behaviour · Rahul Gurung
        
        Re: Jenkins CI behaviour · Markus Mohrhard
      - Re: Jenkins CI behaviour · Eike Rathke
        
        Re: Jenkins CI behaviour · Stephan Bergmann

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.