infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-16346) Log4j builds stuck and unkillable, even though timeout is configured
Date Sun, 27 May 2018 14:21:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-16346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Lambertus updated INFRA-16346:
------------------------------------
    Status: Waiting for user  (was: Waiting for Infra)

Without further information on what the builds were doing before they blocked, there's not
much more for us to troubleshoot. I haven't heard anything about this in 5 weeks, so hopefully
it stopped happening. 

> Log4j builds stuck and unkillable, even though timeout is configured
> --------------------------------------------------------------------
>
>                 Key: INFRA-16346
>                 URL: https://issues.apache.org/jira/browse/INFRA-16346
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Robert Munteanu
>            Assignee: Chris Lambertus
>            Priority: Critical
>
> Two log4j Jenkins jobs are stuck, even though timeouts are configured
> - https://builds.apache.org/job/Log4j%202%203.x/ - 5+ days
> - https://builds.apache.org/job/Log4j%202%202.x/ - 4+ days
> They can't be manually killed either, which is bad as it ties up two executors forever.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message