infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Heinz Marbaise (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-16346) Log4j builds stuck and unkillable, even though timeout is configured
Date Sun, 15 Apr 2018 11:10:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-16346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438664#comment-16438664
] 

Karl Heinz Marbaise commented on INFRA-16346:
---------------------------------------------

So unfortunately the jobs are stuck again...
https://builds.apache.org/job/Log4j%202%202.x/3455/console (Uploaded to Nexus is stuck)..
https://builds.apache.org/job/Log4j%202%203.x/66/console (Upload to Nexus is stuck)...
https://builds.apache.org/job/Syncope-master-deploy/2915/console the same (Upload to Nexus
is stuck)



> 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