[
https://issues.jenkins-ci.org/browse/JENKINS-10401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160758#comment-160758
]
aeschbacher commented on JENKINS-10401:
---------------------------------------
Hi,
We used oe-classic, tag='release-2010.12'
wget http://cgit.openembedded.org/openembedded/snapshot/release-2010.12.tar.bz2
I don't know whether the exact version of OE matters anyway; my thoughts were
that with any _really_ big workspace (as can be workspaces created by
OpenEmbedded: millions of files, 10th of GB) can cause the problem, when
configuring the job with artifacts which can't be found.
Fabrice
> 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
