On 2011-07-27 00:21, Benson Margulies wrote: > I did two things: > > 1) I changed the jobs each to have their own workspace.
Great, thanks. > 2) I changed them to hold the Maven latch, so multiple platforms > cannot run in parallel. Was this needed? Will that mean that the build will take approximately 4 times longer? 4 being the number of platforms. > > On Tue, Jul 26, 2011 at 6:19 PM, Dennis Lundberg <[email protected]> wrote: >> Thanks Benson! >> >> Was this a change specifically for Solaris or was it one change that >> affects all the Labels used? >> >> On 2011-07-27 00:16, Benson Margulies wrote: >>> I fixed this by changing the workspace path for the -m2 job. I turned >>> out to have karma. >>> >>> On Tue, Jul 26, 2011 at 5:54 PM, Dennis Lundberg <[email protected]> wrote: >>>> Hi again >>>> >>>> I see now that we have the same problem on OS X, where both jobs are doing: >>>> >>>> Deleting >>>> /Users/hudson/hudson-slave/maven-site-plugin-3.x/workspace/jdk/JDK 1.5 >>>> (latest)/label/osx/target >>>> >>>> One job was almost certainly copied from the other, when it was set up. >>>> >>>> >>>> On 2011-07-26 23:42, Dennis Lundberg wrote: >>>>> Hi >>>>> >>>>> I've investigated some odd build failures on the Solaris slaves for the >>>>> builds of maven-site-plugin. There are two builds of the same source >>>>> code, but with different versions of Maven. Here are the jobs: >>>>> >>>>> https://builds.apache.org/view/M-R/view/Maven/job/maven-site-plugin-3.x/ >>>>> >>>>> https://builds.apache.org/view/M-R/view/Maven/job/maven-site-plugin-3.x-m2/ >>>>> >>>>> These jobs are set up to build on 4 generic OSes, including the generic >>>>> Solaris label. After analyzing the logs I found that both jobs start by >>>>> doing this: >>>>> >>>>> Deleting >>>>> /zonestorage/hudson/home/hudson/hudson-slave/maven-site-plugin-3.x/workspace/jdk/JDK >>>>> 1.5 (latest)/label/Solaris/target >>>>> >>>>> So when an SVN change triggers a build, or rather two builds in this >>>>> case, the first job is abruptly interrupted by the second one when the >>>>> second one simply deletes the entire workspace of the first. >>>>> >>>>> However the job "maven-site-plugin-3.x-m2" should have it's own >>>>> workspace, called "maven-site-plugin-3.x-m2", on the Solaris slave >>>>> shouldn't it? >>>>> >>>>> Is this something that can be configured or is automagical? >>>>> >>>> >>>> >>>> -- >>>> Dennis Lundberg >>>> >>> >> >> >> -- >> Dennis Lundberg >> > -- Dennis Lundberg
