Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Builds? 
Yes they are. Hudson is failing to see that these processes are still
running. In a past life I recall Jenkins giving a big error if child
processes are still running when jobs are done.

This is the bug BTW http://eclip.se/499471
~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com


On 9 August 2016 at 20:26, Doug Schaefer <dschaefer@xxxxxxxxxxxxxx> wrote:
> Cool. The ones still running, are they running even though the jobs have
> been aborted?
>
> On 2016-08-09, 3:23 PM, "cdt-dev-bounces@xxxxxxxxxxx on behalf of Jonah
> Graham" <cdt-dev-bounces@xxxxxxxxxxx on behalf of jonah@xxxxxxxxxxxxxxxx>
> wrote:
>
>>I think they are all ours. Some of them are Hudson processes and some
>>are maven (presumably the maven are the parents of the eclipse ones),
>>but the suspicious ones all have this or something similar as one of
>>the thread's stack trace (see below). There was one verify build
>>running when I captured this.
>>
>>By my quick count:
>>- total process: 14
>>- maven processes waiting on a Unix process (blocking on
>>java.lang.UNIXProcess.waitFor): 6
>>- number of processes blocked on doing
>>CProjectDescriptionManager.runWspModification: 6
>>- hudson itself: 1
>>- the build that was actually known to be running: 1 (maven was
>>zipping at the time in
>>org.codehaus.plexus.archiver.zip.AbstractZipArchiver.zipFile)
>>
>>I'll file a bug on this for what its worth.
>>
>>"Worker-3" #58 prio=5 os_prio=0 tid=0x00007fc1242d9000 nid=0x1a10 in
>>Object.wait() [0x00007fc10dbd0000]
>>   java.lang.Thread.State: WAITING (on object monitor)
>>at java.lang.Object.wait(Native Method)
>>at java.lang.Object.wait(Object.java:502)
>>at org.eclipse.core.internal.jobs.ThreadJob.waitForRun(ThreadJob.java:270)
>>- locked <0x00000000ff700bc0> (a java.lang.Object)
>>at org.eclipse.core.internal.jobs.ThreadJob.joinRun(ThreadJob.java:197)
>>at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:92)
>>at
>>org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:307)
>>at
>>org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.ru
>>nWspModification(CProjectDescriptionManager.java:483)
>>at
>>org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.ru
>>nWspModification(CProjectDescriptionManager.java:454)
>>at
>>org.eclipse.cdt.internal.core.settings.model.CExternalSettingsManager.sett
>>ingsChanged(CExternalSettingsManager.java:439)
>>at
>>org.eclipse.cdt.internal.core.settings.model.CExternalSettingContainerFact
>>oryWithListener.notifySettingsChange(CExternalSettingContainerFactoryWithL
>>istener.java:48)
>>at
>>org.eclipse.cdt.internal.core.settings.model.CfgExportSettingContainerFact
>>ory.handleEvent(CfgExportSettingContainerFactory.java:253)
>>at
>>org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.no
>>tifyListeners(CProjectDescriptionManager.java:2212)
>>at
>>org.eclipse.cdt.internal.core.settings.model.AbstractCProjectDescriptionSt
>>orage.fireLoadedEvent(AbstractCProjectDescriptionStorage.java:268)
>>at
>>org.eclipse.cdt.internal.core.settings.model.xml.XmlProjectDescriptionStor
>>age.getProjectDescription(XmlProjectDescriptionStorage.java:264)
>>at
>>org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.ge
>>tProjectDescriptionInternal(CProjectDescriptionManager.java:437)
>>at
>>org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.ge
>>tProjectDescription(CProjectDescriptionManager.java:419)
>>at
>>org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.ge
>>tProjectDescription(CProjectDescriptionManager.java:413)
>>at
>>org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.ge
>>tProjectDescription(CProjectDescriptionManager.java:406)
>>at
>>org.eclipse.cdt.core.model.CoreModel.getProjectDescription(CoreModel.java:
>>1424)
>>~~~
>>Jonah Graham
>>Kichwa Coders Ltd.
>>www.kichwacoders.com
>>
>>
>>On 9 August 2016 at 19:11, Doug Schaefer <dschaefer@xxxxxxxxxxxxxx> wrote:
>>> From: <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Marc-André Laperle
>>> <marc-andre.laperle@xxxxxxxxxxxx>
>>> Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
>>> Date: Tuesday, August 9, 2016 at 1:15 PM
>>> To: "elaskavaia.cdt@xxxxxxxxx" <elaskavaia.cdt@xxxxxxxxx>, "CDT General
>>> developers list." <cdt-dev@xxxxxxxxxxx>
>>> Subject: Re: [cdt-dev] Builds?
>>>
>>> That "Abort Action" doesn't seem to exist in Hudson. In the mean time,
>>>I've
>>> made a very simple job that does jps then jstack and outputs all the
>>>stacks.
>>> There seems to be a lot of processes lingering.
>>>
>>>
>>> I assume this is picking up processes from the other HIPPs. We are
>>>sharing
>>> hipp2 with 11 other projects.
>>>
>>>
>>> https://hudson.eclipse.org/cdt/job/jstack-all/
>>>
>>> Marc-Andre
>>>
>>> ________________________________
>>> From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on
>>>behalf of
>>> Alena Laskavaia [elaskavaia.cdt@xxxxxxxxx]
>>> Sent: Tuesday, 09 August 2016 12:53 PM
>>> To: CDT General developers list.
>>> Subject: Re: [cdt-dev] Builds?
>>>
>>> We use "build-timeout plugin".
>>> It adds option Abort the build if it stuck
>>> You can add jstack dump as "Abort Action"
>>>
>>> On Tue, Aug 9, 2016 at 11:21 AM, Doug Schaefer
>>><dschaefer@xxxxxxxxxxxxxx>
>>> wrote:
>>>>
>>>> That¹s weird, but yes. Sergey had two builds running, both of them
>>>>hung in
>>>> tests. Mine was started after and finished first. That¹ll explain it.
>>>>
>>>> Are there any plug-ins that will do a jstack after the build runs past
>>>>a
>>>> certain amount of time so we can see where things are hung?
>>>>
>>>> D.
>>>>
>>>> On 2016-08-09, 11:16 AM, "cdt-dev-bounces@xxxxxxxxxxx on behalf of
>>>>Jonah
>>>> Graham" <cdt-dev-bounces@xxxxxxxxxxx on behalf of
>>>>jonah@xxxxxxxxxxxxxxxx>
>>>> wrote:
>>>>
>>>> >On 9 August 2016 at 16:11, Doug Schaefer <dschaefer@xxxxxxxxxxxxxx>
>>>> > wrote:
>>>> >> The one that hit me yesterday though was a very long delay
>>>>collecting
>>>> >>test
>>>> >> results. It wasn¹t even in our Maven run.
>>>> >
>>>> >Was there another build running still in this case? I think Marc Andre
>>>> >had mentioned something about the cdt-verify builds being dependent on
>>>> >each other to record test results so that effectively the build have
>>>> >to finish in order.
>>>> >_______________________________________________
>>>> >cdt-dev mailing list
>>>> >cdt-dev@xxxxxxxxxxx
>>>> >To change your delivery options, retrieve your password, or
>>>>unsubscribe
>>>> >from this list, visit
>>>> >https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>>
>>>> _______________________________________________
>>>> cdt-dev mailing list
>>>> cdt-dev@xxxxxxxxxxx
>>>> To change your delivery options, retrieve your password, or unsubscribe
>>>> from this list, visit
>>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>
>>>
>>>
>>> _______________________________________________
>>> cdt-dev mailing list
>>> cdt-dev@xxxxxxxxxxx
>>> To change your delivery options, retrieve your password, or unsubscribe
>>>from
>>> this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>_______________________________________________
>>cdt-dev mailing list
>>cdt-dev@xxxxxxxxxxx
>>To change your delivery options, retrieve your password, or unsubscribe
>>from this list, visit
>>https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cdt-dev

Back to the top