On 4/23/16 2:04 PM, Kristian Waagan wrote:
Den 23.04.2016 22.37, skrev Rick Hillegas:
On 4/23/16 10:07 AM, Kristian Waagan wrote:
Den 23.04.2016 17.50, skrev Bryan Pendleton:
On 4/23/2016 7:20 AM, Rick Hillegas wrote:
Does anyone know what the problem is?
No, I'm not sure, sorry.
I can
Den 23.04.2016 22.37, skrev Rick Hillegas:
> On 4/23/16 10:07 AM, Kristian Waagan wrote:
>> Den 23.04.2016 17.50, skrev Bryan Pendleton:
>>> On 4/23/2016 7:20 AM, Rick Hillegas wrote:
Does anyone know what the problem is?
>>> No, I'm not sure, sorry.
>>>
>>> I can see that Jenkins build
On 4/23/16 10:07 AM, Kristian Waagan wrote:
Den 23.04.2016 17.50, skrev Bryan Pendleton:
On 4/23/2016 7:20 AM, Rick Hillegas wrote:
Does anyone know what the problem is?
No, I'm not sure, sorry.
I can see that Jenkins build #261 was automatically initiated
after your patch for DERBY-6883
Den 23.04.2016 17.50, skrev Bryan Pendleton:
> On 4/23/2016 7:20 AM, Rick Hillegas wrote:
>> Does anyone know what the problem is?
>>
>
> No, I'm not sure, sorry.
>
> I can see that Jenkins build #261 was automatically initiated
> after your patch for DERBY-6883 was committed, and the build
>
On 4/23/2016 7:20 AM, Rick Hillegas wrote:
Does anyone know what the problem is?
No, I'm not sure, sorry.
I can see that Jenkins build #261 was automatically initiated
after your patch for DERBY-6883 was committed, and the build
job finished with SUCCESS:
Does anyone know what the problem is?
Thanks,
-Rick