db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mamta Satoor <msat...@gmail.com>
Subject Re: Jenkins failure (was: Re: Delivery Status Notification (Failure))
Date Thu, 09 Aug 2012 16:18:50 GMT
Thanks, Kristian.

On Wed, Aug 8, 2012 at 11:16 PM, Kristian Waagan
<kristian.waagan@oracle.com> wrote:
> On 09.08.2012 00:33, Mamta Satoor wrote:
>>
>> I need help understanding this failure. I did a backport to 10.9 for
>> DERBY-5839 and derbyall (including CompatibilityTest) has run fine on
>> my machine. The following report says there was a failure on 10.9 but
>> it is shwoing only part of the failure. Is there a place I can check
>> the test result myself?
>
>
> Hi Mamta,
>
> Yes, see https://builds.apache.org/view/A-F/view/Derby/ (or
> https://builds.apache.org/).
> You can also look at the full output of specific runs. For suites.All you
> must look at the report for the JUnit tests.
>
>> Has the test failed again on 10.9 again? The
>> internal build and test of 10.9 codeline hasn't shown any errors.
>
>
> It looks to me like there were some kind of temporary issues with the
> Jenkins infrastructure.
> derbyAll had trouble with file permissions (no idea how that happened), and
> suites.All suffered from network issues (22 failed tests, all in
> DatabaseMetaDataTest).
>
> The tests ran successfully once after the failed/unstable runs, but I
> started them again now for good measure.
>
>
> Regards,
> --
> Kristian
>
>>
>> thanks,
>> Mamta
>>
>> On Wed, Aug 8, 2012 at 3:32 PM, Mail Delivery Subsystem
>> <mailer-daemon@googlemail.com>  wrote:
>>>
>>> Delivery to the following recipient failed permanently:
>>>
>>>       jenkins@builds.apache.org
>>>
>>> Technical details of permanent failure:
>>> Google tried to deliver your message, but it was rejected by the
>>> recipient domain. We recommend contacting the other email provider for
>>> further information about the cause of this error. The error that the other
>>> server returned was: 554 554 5.7.1<jenkins@builds.apache.org>: Relay access
>>> denied (state 13).
>>>
>>> ----- Original message -----
>>>
>>> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
>>>          d=gmail.com; s=20120113;
>>>
>>> h=mime-version:in-reply-to:references:date:message-id:subject:from:to
>>>           :content-type;
>>>          bh=iUd0xL5U6wxxcoKl8GjuYJj44iXDpbApOIfK8NAUw5Q=;
>>>
>>> b=AZCetmtfX+CDjufsz2zUnJx/1VnPzktQaC7WW4u5P1xBQN7DOSBcK/LUKIDFFylgjS
>>>
>>> QwSTvn5YKZ4MRSPJXVy3JK0M6BaNARjaWVePlqp2y8laVIpLj8adnfj6tVRURfhdSAER
>>>
>>> z2rUXLGtgrfiSHsDUXvH7N5TvgAn3b2t6cPFZaIN5EpQ3ZhYYXmxslU29b8KgHAJowx6
>>>
>>> K4tHn0IxavFqddxZt58ZSR8glBgY1KlDQM8ASFoLvJ0KL7spzdoKS4rJe/f0gWdraFRb
>>>
>>> Qy1ElqWeAsATBslfpvcQlqCE3AjQC4kX+scfUaWmhPtrBdXDdInVV4mPO4QgWNtG0YfX
>>>           G7Jw==
>>> MIME-Version: 1.0
>>> Received: by 10.68.234.70 with SMTP id uc6mr3861258pbc.44.1344465166224;
>>> Wed,
>>>   08 Aug 2012 15:32:46 -0700 (PDT)
>>> Received: by 10.142.51.1 with HTTP; Wed, 8 Aug 2012 15:32:46 -0700 (PDT)
>>>
>>> In-Reply-To:<1764001049.1067.1344391677885.JavaMail.hudson@aegis.apache.org>
>>>
>>> References:<1764001049.1067.1344391677885.JavaMail.hudson@aegis.apache.org>
>>> Date: Wed, 8 Aug 2012 15:32:46 -0700
>>>
>>> Message-ID:<CAFy7pk8C5WVxQ--8xym23wW9An18faHmJz2DWncihoec49o2wg@mail.gmail.com>
>>> Subject: Re: Build failed in Jenkins: Derby-10.9-derbyall #19
>>> From: Mamta Satoor<msatoor@gmail.com>
>>> To: Apache Jenkins Server<jenkins@builds.apache.org>
>>> Content-Type: text/plain; charset=ISO-8859-1
>>>
>>> I need help understanding this failure. I did a backport to 10.9 for
>>> DERBY-5839 and derbyall (including CompatibilityTest) has run fine on
>>> my machine. The following report says there was a failure on 10.9 but
>>> it is shwoing only part of the failure. Is there a place I can check
>>> the test result myself? Has the test failed again on 10.9 again? The
>>> internal build and test of 10.9 codeline hasn't shown any errors.
>>>
>>> thanks,
>>> Mamta
>>>
>>> On Tue, Aug 7, 2012 at 7:07 PM, Apache Jenkins Server
>>> <jenkins@builds.apache.org>  wrote:
>>>>
>>>> See<https://builds.apache.org/job/Derby-10.9-derbyall/19/changes>
>>>>
>>>> Changes:
>>>>
>>>> [mamta] DERBY-5839 (dblook run on toursdb fails on triggers with
>>>> java.lang.StringIndexOutOfBoundsException in dblook.log)
>>>>
>>>> Backporting from trunk to 10.9
>>>>
>>>> ------------------------------------------
>>>> [...truncated 10665 lines...]
>>>> <  false
>>>> 2100 del
>>>> <  OLDTABLE
>>>> 2101 del
>>>> <  null
>>>> 2102 del
>>>> <  -----
>>>> 2103 del
>>>> <  <systemid>
>>>> 2104 del
>>>> <  TRIG2
>>>> 2105 del
>>>> <  Foo Bar
>>>> 2106 del
>>>> <  <systemid>
>>>> 2107 del
>>>> <  D
>>>> 2108 del
>>>> <  B
>>>> 2109 del
>>>> <  S
>>>> 2110 del
>>>> <  E
>>>> 2111 del
>>>> <  T1
>>>> 2112 del
>>>> <  null
>>>> 2113 del
>>>> <  <systemid>
>>>> 2114 del
>>>> <  null
>>>> 2115 del
>>>> <  values (1), (2)
>>>> 2116 del
>>>> <  false
>>>> 2117 del
>>>> <  false
>>>> 2118 del
>>>> <  null
>>>> 2119 del
>>>> <  null
>>>> 2120 del
>>>> <  -----
>>>> 2121 del
>>>> <  <systemid>
>>>> 2122 del
>>>> <  TRIGFOUR
>>>> 2123 del
>>>> <  APP
>>>> 2124 del
>>>> <  <systemid>
>>>> 2125 del
>>>> <  U
>>>> 2126 del
>>>> <  A
>>>> 2127 del
>>>> <  S
>>>> 2128 del
>>>> <  E
>>>> 2129 del
>>>> <  X
>>>> 2130 del
>>>> <  null
>>>> 2131 del
>>>> <  <systemid>
>>>> 2132 del
>>>> <  (1)
>>>> 2133 del
>>>> <  insert into removed select * from old where x not in (select x from
>>>> new where x<  10)
>>>> 2134 del
>>>> <  true
>>>> 2135 del
>>>> <  true
>>>> 2136 del
>>>> <  OLD
>>>> 2137 del
>>>> <  NEW
>>>> 2138 del
>>>> <  -----
>>>> 2139 del
>>>> <  <systemid>
>>>> 2140 del
>>>> <  TRIGONE
>>>> 2141 del
>>>> <  APP
>>>> 2142 del
>>>> <  <systemid>
>>>> 2143 del
>>>> <  I
>>>> 2144 del
>>>> <  A
>>>> 2145 del
>>>> <  R
>>>> 2146 del
>>>> <  E
>>>> 2147 del
>>>> <  T3

Mime
View raw message