It's a question of spare time, so can't tell ...

2012/11/12 Reuben Gow <[email protected]>

> Any chance of getting a build with this fix in? I will happily test it for
> you.
>
>
> On Monday, 12 November 2012 10:26:51 UTC, Nicolas De loof wrote:
>
>> there's a permission issue with parallel() I have to fix and may explain
>> this issue, not sure yet.
>> I don't have any other assumption what could make this fail
>>
>> 2012/11/12 Reuben Gow <[email protected]>
>>
>> Hi Nicolas,
>>>
>>> Have you had chance to look at this issue?
>>>
>>>
>>> On Friday, 21 September 2012 09:58:06 UTC+1, Nicolas De loof wrote:
>>>
>>>> This is not expected. First unstable/failed build in a sequence is
>>>> supposed to stop the execution.
>>>> what version of the plugin are you using ? I committed an attempt to
>>>> sanitize thread-safety in 0.5
>>>> what OS is master running on ?
>>>>
>>>> 2012/9/21 Reuben Gow <[email protected]>
>>>>
>>>> Hi,
>>>>>
>>>>> I am utilising the build flow plugin an have noticed an issue (that is
>>>>> also mentioned in the comments on the wiki but has no response).
>>>>>
>>>>> My DSL looks like this:
>>>>>
>>>>> parallel (
>>>>>> {build( "software_32bit" )},
>>>>>> {build( "software_64bit" )}
>>>>>> )
>>>>>> parallel (
>>>>>> {build( "other_software_that_depends_**o**n_upstream_32bit" ) },
>>>>>> {build( "other_software_that_depends_**o**n_upstream_32bit" ) }
>>>>>> )
>>>>>> parallel (
>>>>>> {build( "some_test_1" )},
>>>>>> {build( "some_test_2" )},
>>>>>> {build( "some_test_3" )},
>>>>>> {build( "some_test_4" )}
>>>>>> )
>>>>>
>>>>>
>>>>> My problem is that other_software_that_depends_**on**_upstream_32bit
>>>>> or other_software_that_**depends**_on_upstream_32bit has failed yet
>>>>> the tests still get kicked off. I was expecting the job to terminate if 
>>>>> one
>>>>> of the parallel builds failed.
>>>>>
>>>>> Is this expected behaviour?
>>>>>
>>>>
>>>>
>>

Reply via email to