The BFA uses thread-pools in two different places; One pool is created for 
every finished build to scan the log in parallel (we have a big number of 
builds with 10MB log files or more, so that helped with performance). But those 
pools should be closed down when the scanning is done.
The other is during startup when it needs to convert old build data to the new 
format (<1.3.0 to 1.4.0). That thread pool is not closed because of the lazy 
loading of builds in newer Jenkins cores.
The conversion thread pool should not be created if Jenkins starts up with only 
newer format of build records.


Robert Sandell
Software Tools Engineer - SW Environment and Product Configuration
Sony Mobile Communications

From: Yitzhak Zuriel [mailto:zurie...@gmail.com]
Sent: den 18 mars 2013 11:29
To: jenkinsci-users@googlegroups.com
Cc: Westling, Tomas; Sandell, Robert; jhoomshar...@netscape.net
Subject: Re: Build failure Analyzer Plugin’s odd behaviour

I'm reviving this old thread because I have some new information that was not 
written here before. We moved on to work with a different server and continued 
to monitor and study the problematic one.using some of the Java tools.  And we 
saw that on the machine with the sluggish response there was a proliferation of 
threads in Java that were not being closed. Has anyone seen this behavior, and 
has an explanation of what to do about it?


On Thursday, January 24, 2013 8:44:23 AM UTC+2, 
jhooms...@netscape.net<mailto:jhooms...@netscape.net> wrote:
No ours not matrix project

I think my issue is same as JENKINS-15948, icon image url looks to be broken, 
the url getting generated for bulb icon image is

http://[host]/jenkins//plugin/build-failure-analyzer/images/16x16/information.png<http://[host]/jenkins/plugin/build-failure-analyzer/images/16x16/information.png>

but in actual it should be

http://[host]/plugin/build-failure-analyzer/images/16x16/information.png

I am using build analyzer plugin v1.3.0

-----Original Message-----
From: Westling, Tomas <tomas.w...@sonymobile.com<javascript:>>
To: 'jhooms...@netscape.net<javascript:>' 
<jhooms...@netscape.net<javascript:>>; jenkinsci-users 
<jenkins...@googlegroups.com<javascript:>>
Cc: Sandell, Robert <robert....@sonymobile.com<javascript:>>
Sent: Wed, Jan 23, 2013 5:30 pm
Subject: RE: Build failure Analyzer Plugin’s odd behaviour
Is your project a matrix project? If so then I’ve found the bug and will upload 
a bug fix.

Br Tomas

From: jhooms...@netscape.net<javascript:> 
[mailto:jh...@netscape.net<javascript:>]
Sent: den 23 januari 2013 09:42
To: Westling, Tomas; jenkins...@googlegroups.com<javascript:>
Cc: Sandell, Robert
Subject: Re: Build failure Analyzer Plugin’s odd behaviour


Attaching screen shot related to missing bulb icon

-----Original Message-----
From: Westling, Tomas <tomas.w...@sonymobile.com<javascript:>>
To: 'jhooms...@netscape.net<javascript:>' 
<jhooms...@netscape.net<javascript:>>; jenkinsci-users 
<jenkins...@googlegroups.com<javascript:>>
Cc: Sandell, Robert <robert....@sonymobile.com<javascript:>>
Sent: Tue, Jan 22, 2013 5:59 pm
Subject: RE: Build failure Analyzer Plugin’s odd behaviour
Hi Jhoom,

issue number 3 is a known problem which we are working on. The issue is with
logs that are large enough so that the build log has to be split up and the 
“full log”
is visible. We are going to release a bug fix for this issue soon.

As for the other two issues I am not quite sure what you mean, are the bulb 
icons missing for
builds that have identified the problem? Could you attach a screenshot of the 
problem?

Br Tomas

From: jhooms...@netscape.net<javascript:> 
[mailto:jh...@netscape.net<javascript:>]
Sent: den 22 januari 2013 12:58
To: jenkins...@googlegroups.com<javascript:>
Cc: Sandell, Robert; Westling, Tomas
Subject: Build failure Analyzer Plugin’s odd behaviour

Hi
I am seeing strange problem on my Jenkins 1.496 server running on Solaris box,
1.      I cannot see Build Failure Analyzer plugin bulb icon under “Build 
History” section instate of icon a text “Identified problems” is visible
2.      When I click on logs under “Build History” for a particular 
failed/unstable build again bulb icon is missing only following messages are 
visible:

Identified problems

Unit Test Failure
            Contains test case failure
            Indication 1 Indication 2
3.      When I click on “Indication” links, it takes me to build logs but did 
not show the problem with red highlight, I need to click on “Full log” link and 
then navigate to build log to look for highlighted error.

Anyone faced this problem in their dev environment with Build Failure Analyzer, 
if yes can anyone help me out and resolving this issue.

Thanks,
Jhoom

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to