On 12/01/2010, Phil Steitz wrote:
> sebb wrote:
> > On 12/01/2010, Phil Steitz wrote:
> >> sebb wrote:
> >> > On 11/01/2010, Phil Steitz wrote:
> >> >> Phil Steitz wrote:
> >> >> > Posting the last failed build output while it is, umstill
> available:
> >> >
> >> > I assume thi
sebb wrote:
> On 12/01/2010, Phil Steitz wrote:
>> sebb wrote:
>> > On 11/01/2010, Phil Steitz wrote:
>> >> Phil Steitz wrote:
>> >> > Posting the last failed build output while it is, umstill
>> available:
>> >
>> > I assume this is from:
>> >
>> >
>> http://vmbuild.apache.org/cont
On 12/01/2010, Phil Steitz wrote:
> sebb wrote:
> > On 11/01/2010, Phil Steitz wrote:
> >> Phil Steitz wrote:
> >> > Posting the last failed build output while it is, umstill
> available:
> >
> > I assume this is from:
> >
> >
> http://vmbuild.apache.org/continuum/buildResult.action
sebb wrote:
> On 11/01/2010, Phil Steitz wrote:
>> Phil Steitz wrote:
>> > Posting the last failed build output while it is, umstill available:
>
> I assume this is from:
>
> http://vmbuild.apache.org/continuum/buildResult.action?buildId=267625&projectId=22
>
>> >
>> > Multithread test t
On 11/01/2010, Phil Steitz wrote:
> Phil Steitz wrote:
> > Posting the last failed build output while it is, umstill available:
I assume this is from:
http://vmbuild.apache.org/continuum/buildResult.action?buildId=267625&projectId=22
> >
> > Multithread test time = 489 ms. Threads: 20. L
Phil Steitz wrote:
> Posting the last failed build output while it is, umstill available:
>
> Multithread test time = 489 ms. Threads: 20. Loops: 20. Hold time:
> 200. Maxwait: 100. Done: 11. Did not run: 0. Failed: 9. expectError:
> true
> StartupDelay: 0. ConnectTime: 3. Runtime: 203. Loops:
Posting the last failed build output while it is, umstill available:
Multithread test time = 489 ms. Threads: 20. Loops: 20. Hold time:
200. Maxwait: 100. Done: 11. Did not run: 0. Failed: 9. expectError:
true
StartupDelay: 0. ConnectTime: 3. Runtime: 203. Loops: 1. State:
Done. thrown: null.
sebb wrote:
> On 10/01/2010, Phil Steitz wrote:
>> sebb wrote:
>> > On 10/01/2010, Phil Steitz wrote:
>> >> sebb wrote:
>> >> > On 10/01/2010, Phil Steitz wrote:
>> >> >> sebb wrote:
>> >> >> > Thanks.
>> >> >> >
>> >> >> > Looks like I did not complete the fixes properly when I a
On 10/01/2010, Phil Steitz wrote:
> sebb wrote:
> > On 10/01/2010, Phil Steitz wrote:
> >> sebb wrote:
> >> > On 10/01/2010, Phil Steitz wrote:
> >> >> sebb wrote:
> >> >> > Thanks.
> >> >> >
> >> >> > Looks like I did not complete the fixes properly when I added the
> >> >> >
sebb wrote:
> On 10/01/2010, Phil Steitz wrote:
>> sebb wrote:
>> > On 10/01/2010, Phil Steitz wrote:
>> >> sebb wrote:
>> >> > Thanks.
>> >> >
>> >> > Looks like I did not complete the fixes properly when I added the
>> >> > loopOnce parameter to PoolTest.
>> >>
>> >> I think I foun
On 10/01/2010, Phil Steitz wrote:
> sebb wrote:
> > On 10/01/2010, Phil Steitz wrote:
> >> sebb wrote:
> >> > Thanks.
> >> >
> >> > Looks like I did not complete the fixes properly when I added the
> >> > loopOnce parameter to PoolTest.
> >>
> >> I think I found (and fixed) another p
sebb wrote:
> On 10/01/2010, Phil Steitz wrote:
>> sebb wrote:
>> > Thanks.
>> >
>> > Looks like I did not complete the fixes properly when I added the
>> > loopOnce parameter to PoolTest.
>>
>> I think I found (and fixed) another problem. See r897720.
>
> The wait in question is purely to
On 10/01/2010, Phil Steitz wrote:
> sebb wrote:
> > Thanks.
> >
> > Looks like I did not complete the fixes properly when I added the
> > loopOnce parameter to PoolTest.
>
> I think I found (and fixed) another problem. See r897720.
The wait in question is purely to allow the threads to star
sebb wrote:
> Thanks.
>
> Looks like I did not complete the fixes properly when I added the
> loopOnce parameter to PoolTest.
I think I found (and fixed) another problem. See r897720.
>
> It was quite tricky following the Continuum build output, as the date
> was 2 days behind, and the mail fo
14 matches
Mail list logo