Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 454311 - Eclipse Platform build processes appear "dead" (D status)
Summary: Eclipse Platform build processes appear "dead" (D status)
Status: RESOLVED WORKSFORME
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Servers (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 blocker (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Webmaster CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 454272
Blocks:
  Show dependency tree
 
Reported: 2014-12-05 21:31 EST by David Williams CLA
Modified: 2014-12-05 22:52 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2014-12-05 21:31:10 EST
+++ This bug was initially created as a clone of Bug #454272 +++

I've created this as a clone, since I think the "problem" may be similar ... about NFS mounts "going away"? Though, build.eclipse.org is still responsive and loads look fine. 

BUT, the next attempt at a build is going on 9 hours now ... typically takes 3 or so. 

And, when I look a the "processes" for 'e4Build' I see a couple that show "D" status, and one of those appears to have been that way for 7 hours. 

Here's "top" lines (with partial command lines). 

20390 e4Build   20   0 15204 1132  808 D      0  0.0   0:07.34 find CONTRIBUTING README.md bootstrap devutils eclipse-platform-parent eclipse.jdt eclipse.jdt.core eclipse.jdt.core.binaries

29452 e4Build   20   0 98948  16m  12m D      0  0.1   0:01.34 git status
Comment 1 David Williams CLA 2014-12-05 22:52:19 EST
Well, never mind, I guess. Unless you did something ... but, maybe I was mis-reading the "times" on those in "D state". 

Those processes have moved on ... but, I have no idea why this build would be taking so much longer than usual. Going 8 hours and 47 minutes, now that I've figured out how to print the elapsed time clearly. (but appears ps does not know how to sort it :(  

$ ps --header ww --sort etime -o pid,user,etime,s,args -u e4Build | grep "builds/4M"
  557 e4Build        48:11 S java -Djava.io.tmpdir=/shared/eclipse/builds/4M/tmp -jar /shared/eclipse/builds/4M/siteDir/eclipse/downloads/drops4/M20141205-1400/org.eclipse.releng.basebuilder/plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar -data /shared/eclipse/builds/4M/siteDir/eclipse/downloads/drops4/M20141205-1400/workspace-comparatorLogs -application org.eclipse.ant.core.antRunner -buildfile /shared/eclipse/builds/4M/siteDir/eclipse/downloads/drops4/M20141205-1400/eclipse.platform.releng.aggregator/eclipse.platform.releng.tychoeclipsebuilder/eclipse/buildScripts/api-tools-builder.xml -DbuildDirectory=/shared/eclipse/builds/4M/siteDir/eclipse/downloads/drops4 -DpostingDirectory=/shared/eclipse/builds/4M/siteDir/eclipse/downloads/drops4 -DEBuilderDir=/shared/eclipse/builds/4M/siteDir/eclipse/downloads/drops4/M20141205-1400/eclipse.platform.releng.aggregator/eclipse.platform.releng.tychoeclipsebuilder -DbuildId=M20141205-1400 -DbuildLabel=M20141205-1400 -DbuildWorkingArea=/shared/eclipse/builds/4M/gitCache/eclipse.platform.releng.aggregator -DpreviousBaseURL=http://download.eclipse.org/eclipse/downloads/drops4/R-4.4-201406061215/eclipse-SDK-4.4-win32.zip -DpreviousBaselineName=Eclipse-SDK-4.4 -DpreviousBaselineFilename=eclipse-SDK-4.4-win32.zip -Djava.io.tmpdir=/shared/eclipse/builds/4M/tmp apiToolsReports
 9671 e4Build     08:47:28 S bash /shared/eclipse/builds/4M/production/master-build.sh /shared/eclipse/builds/4M/production/build_eclipse_org.shsource
19871 e4Build     01:58:24 S bash /shared/eclipse/builds/4M/production/publish-eclipse.sh /shared/eclipse/builds/4M/siteDir/eclipse/downloads/drops4/M20141205-1400/buildproperties.shsource