[
https://issues.jenkins-ci.org/browse/JENKINS-10401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lloydchang reassigned JENKINS-10401:
------------------------------------
Assignee: aeschbacher (was: lloydchang)
Hello aeschbacher:
I am re-assigning to you for more information.
When your time permtis, please describe the the version of OpenEmbedded (oe)
where this problem occurred with Jenkins version 1.420. Specifically, were you
using oe-classic or oe-core?
If you could provide step-by-step instructions of the `git` commands of the
oe-core tag that you cloned locally, along with the Jenkins version you would
like to use (if newer than 1.420), it would help me focus on reproducing this
issue using your desired oe-core git tag and Jenkins version going forward.
Thank you,
Lloyd
> jenkins using 100% CPU if trying to archive unexisting artifact
> ---------------------------------------------------------------
>
> Key: JENKINS-10401
> URL: https://issues.jenkins-ci.org/browse/JENKINS-10401
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Affects Versions: current
> Environment: Linux (debian squeeze 32bits)
> Reporter: aeschbacher
> Assignee: aeschbacher
>
> [Jenkins ver. 1.420]
> If a jobs tries to archive an inexisting artifact, the jenkins process uses
> 100% CPU forever, until we do a '/etc/init.d/jenkins stop'
> The web interface can not anymore be used
> The problem is not new in 1.420, but exists for a long time, already in
> hudson (I did actually never see any linux version not having this problem).
> A significant information is that we have a huge workspace (up to 45G - we
> build distros with OpenEmbedded) shared between the jobs
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
