(Tibor; I'm taking this to the mailing list)
It would appear that we are leaking file handles/resources when being killed by jenkins. This is not entirely surprising, since this is notoriously hard to get right. Does anyone know how the timeout in jenkins kills our process ? (If it's the equivalent of kill -9 we're in trouble no matter what, but usually some softer means is used first....) I'll montor for resurce leaks while killing processes this weekend to see if I can find anything. Kristian ---------- Forwarded message ---------- From: Tibor Digana <tibor.dig...@googlemail.com> Date: 2015-10-22 21:05 GMT+02:00 Subject: Re: to delete windows build ? To: Andreas Gudian <andreas.gud...@gmail.com> Kopi: Kristian Rosenvold <kristian.rosenv...@gmail.com> >>Could it be the ancient shadefire-version that causes hanging processes in >>our integration tests on those windows nodes? I do not know since I could not reproduce this issue on my system. IMHO the files are locked after the job has timed out. My words in JIRA: "The build setup says that the build timeout is 69 min. The bild was running 64 which is very close." I should reopen the bug and ask INFRA to clean up the workspace. I expected INFRA to find out the root cause. The time out issue is a guess. Cheers Tibor On Thu, Oct 22, 2015 at 6:12 PM, Andreas Gudian <andreas.gud...@gmail.com> wrote: > > Hi, > > A build that fails constantly has no value at all. A working Windows build on > the other hand would be something that I'd consider quite important - process > spawning, communication and termination can behave slightly different under > different OS's. > > Tibor and I are on Windows, but if someone else working on OSX or Linux > starts changing something in that area, the missing Windows builds (or the > currently unusable jobs) could create a blind spot. > > Could it be the ancient shadefire-version that causes hanging processes in > our integration tests on those windows nodes? I never had any problems with > it on my local machines, though. > > Cheers, > Andreas > > > Am Donnerstag, 22. Oktober 2015 schrieb Tibor Digana : >> >> Hi, >> >> Our CI build permanently fails due to locked files in workspace. >> https://builds.apache.org/job/maven-surefire-windows/ >> I reported an issue but this did not help >> https://issues.apache.org/jira/browse/INFRA-10547 >> Do we need Windows build? >> It looks like there is only Windows1 and Windows2 machine. One is too slow >> and the next one has this problem with file system. >> I prefer working Win agent but the INFRA does not care. >> >> -- >> Cheers >> Tibor -- Cheers Tibor --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
