You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Hiranya Jayathilaka <hi...@gmail.com> on 2009/03/07 07:39:15 UTC

[GSoC] Derby Test and Fix

Hi Folks,
I'm Hiranya Jayathilaka, an undergraduate from University of Moratuwa, Sri
Lanka. I was going through the list of GSoC project ideas from ASF and I
noticed the Derby-Test and Fix project listed there. I'm really interested
in taking up this task since it will give me a great opportunity to work
with a large fraction of the Derby code base. Also I believe my
contributions in this project can make a significant impact on the usability
of the software.

I have used Apache Derby in the past a lot but haven't really looked into
the source code. So now I'm in the process of studying the Derby code base.
Since it is a fairly large code base I would appreciate some help in getting
familiar with the code. Please do let me know where I should get started.
Any special packages/modules/classes I should look into?

Also if there is anything in particular I should be concerned of with
respect to this project (any critical bugs etc I should focus on) please
advice me. Any response is most appreciated.


Thanks,
Hiranya

Re: [GSoC] Derby Test and Fix

Posted by Kathey Marsden <km...@sbcglobal.net>.
Hiranya Jayathilaka wrote:
> Thanks for the guide lines.
>
It is strange I didn't get your mail describing your test issue and 
asking this question. I do see it in the archives, however, so I assume 
it is some problem on my end, but since there does seem to be a problem, 
if it ever seems like I am ignoring you, give me a ping as I may not 
have seen your mail.

You asked:
>I'll start preparing the proposal as soon as possible. Before I do I 
want to know whether >there are any expectations from the community that 
I should be aware of. Any special >issues, project goals that I should 
be concerned of?

In your proposal please make sure you call out.
    - Work you have done on Derby already, including reading 
documentation and setting up your build and test environment.
    - Work you plan to do on Derby. Site specific issues you would like 
to work on. If you like I can help you identify ones that might be 
appropriate.
    - Your availability during the GSoC period. Ideally specify how many 
hours per week you can work and any dates you will be out on vacation etc.

It would be ideal if you could complete or at least get started on an 
issue before April 3 when ranking begins so we can see some example of 
your work and interaction with the community on technical issues.

I have offered to review other students' proposals and would be happy to 
review yours before you submit if you would like input.

Thanks

Kathey


Re: [GSoC] Derby Test and Fix

Posted by Hiranya Jayathilaka <hi...@gmail.com>.
Hi Myrna,

I'll further analyze the problem and provide you folks with a more detailed
report. Thanks for the guide lines.

Thanks,
Hiranya

On Mon, Mar 23, 2009 at 3:38 PM, Myrna van Lunteren
<m....@gmail.com>wrote:

> On Mon, Mar 23, 2009 at 12:39 AM, Hiranya Jayathilaka
> <hi...@gmail.com> wrote:
> ...
> > Most test suites turned out just fine with 100% success rate. But when
> > trying out the derbyall suite there was a one test failure. I have
> attached
> > the report for your reference.
>
> If that is all the diff you saw, it's not the same as any of the other
> issues we've seen (most have been jvm related I believe, see for
> instance DERBY-3643).
> Perhaps there is a trace stack. These master-based tests should have a
> the testfiles saved on error - you need to drill down to in the
> derbyall tree to where the test files and look for bootLock.tmp.
>
> HTH,
> Myrna
>

Re: [GSoC] Derby Test and Fix

Posted by Myrna van Lunteren <m....@gmail.com>.
On Mon, Mar 23, 2009 at 12:39 AM, Hiranya Jayathilaka
<hi...@gmail.com> wrote:
...
> Most test suites turned out just fine with 100% success rate. But when
> trying out the derbyall suite there was a one test failure. I have attached
> the report for your reference.

If that is all the diff you saw, it's not the same as any of the other
issues we've seen (most have been jvm related I believe, see for
instance DERBY-3643).
Perhaps there is a trace stack. These master-based tests should have a
the testfiles saved on error - you need to drill down to in the
derbyall tree to where the test files and look for bootLock.tmp.

HTH,
Myrna

Re: [GSoC] Derby Test and Fix

Posted by Hiranya Jayathilaka <hi...@gmail.com>.
Hi Folks,

This is just a progress update. I checked out the Derby trunk and built the
jars from the source. Then I tried out each and every test suite possible.
Most test suites turned out just fine with 100% success rate. But when
trying out the derbyall suite there was a one test failure. I have attached
the report for your reference.

I also had a look at the issues which are marked 'new comer' and I already
see a couple of interesting ones that I can start working on. I'll look into
them as soon as the ApacheCon-EU is over. Talking about ApacheCon EU, I have
made arrangements with Dag Wanwik to meet up on Tuesday (24th March). Thanks
Dag for contacting me off-list and making the necessary arrangements. I'm
sure we can further discuss how things are at the Derby community these days
once we meet up.

I'll start preparing the proposal as soon as possible. Before I do I want to
know whether there are any expectations from the community that I should be
aware of. Any special issues, project goals that I should be concerned of?

Thanks,
Hiranya




On Tue, Mar 17, 2009 at 5:20 AM, Dag H. Wanvik <Da...@sun.com> wrote:

> Francois Orsini <fr...@gmail.com> writes:
>
> > Hi Hiranya,
> >
> > I believe Dag Wanvik will be at ApacheCon in Amsterdam this year. You
> guys
> > should be able to hook-up.
>
> That's correct; I will be there on Tuesday night (March 24). See you
> there.
>
> Dag
>

Re: [GSoC] Derby Test and Fix

Posted by "Dag H. Wanvik" <Da...@Sun.COM>.
Francois Orsini <fr...@gmail.com> writes:

> Hi Hiranya,
>
> I believe Dag Wanvik will be at ApacheCon in Amsterdam this year. You guys
> should be able to hook-up.

That's correct; I will be there on Tuesday night (March 24). See you
there.

Dag

Re: [GSoC] Derby Test and Fix

Posted by Francois Orsini <fr...@gmail.com>.
Hi Hiranya,

I believe Dag Wanvik will be at ApacheCon in Amsterdam this year. You guys
should be able to hook-up.

Cheers

--francois

On Sun, Mar 15, 2009 at 9:55 PM, Hiranya Jayathilaka
<hi...@gmail.com>wrote:

> Hi Folks,
> Sorry for not keeping you up-to-date on my progress. But I've been reading
> Derby documentation and trying out various test suites. I must say that
> Derby is one of the best documented open source projects I've ever
> encountered :) Really good work folks. I've tried out most of the test
> suites so far (I'm running them one by one) and I can already see a couple
> of test failures. I will post a detailed report on my observations very
> soon.
>
> Also I'd like to know that will any of you folks be at Amsterdam for
> upcoming ApacheCon? I'll be there and would love to get to know you devs
> better.
>
> Thanks,
> Hiranya
>
>
> On Sat, Mar 7, 2009 at 8:43 PM, Bryan Pendleton <bpendleton@amberpoint.com
> > wrote:
>
>>  code base. Since it is a fairly large code base I would appreciate some
>>> help in getting familiar with the code.
>>>
>>
>> Hello Hiranya, welcome to Derby!
>>
>> One place to get started is to look at the open issues in JIRA which have
>> been flagged as "newcomer":
>> https://issues.apache.org/jira/browse/DERBY/component/12310640
>>
>> You might see something there which is interesting and suggests an initial
>> place to explore.
>>
>> Another good thing to do is to verify that you can successfully build
>> the code from scratch and run all the regression tests. The Derby
>> regression
>> suite is quite thorough, and you should be able to get a 100% pass rate.
>>
>> Let us know of your progress!
>>
>> bryan
>>
>>
>

Re: [GSoC] Derby Test and Fix

Posted by Hiranya Jayathilaka <hi...@gmail.com>.
Hi Folks,
Sorry for not keeping you up-to-date on my progress. But I've been reading
Derby documentation and trying out various test suites. I must say that
Derby is one of the best documented open source projects I've ever
encountered :) Really good work folks. I've tried out most of the test
suites so far (I'm running them one by one) and I can already see a couple
of test failures. I will post a detailed report on my observations very
soon.

Also I'd like to know that will any of you folks be at Amsterdam for
upcoming ApacheCon? I'll be there and would love to get to know you devs
better.

Thanks,
Hiranya


On Sat, Mar 7, 2009 at 8:43 PM, Bryan Pendleton
<bp...@amberpoint.com>wrote:

> code base. Since it is a fairly large code base I would appreciate some
>> help in getting familiar with the code.
>>
>
> Hello Hiranya, welcome to Derby!
>
> One place to get started is to look at the open issues in JIRA which have
> been flagged as "newcomer":
> https://issues.apache.org/jira/browse/DERBY/component/12310640
>
> You might see something there which is interesting and suggests an initial
> place to explore.
>
> Another good thing to do is to verify that you can successfully build
> the code from scratch and run all the regression tests. The Derby
> regression
> suite is quite thorough, and you should be able to get a 100% pass rate.
>
> Let us know of your progress!
>
> bryan
>
>

Re: [GSoC] Derby Test and Fix

Posted by Bryan Pendleton <bp...@amberpoint.com>.
> code base. Since it is a fairly large code base I would appreciate some 
> help in getting familiar with the code. 

Hello Hiranya, welcome to Derby!

One place to get started is to look at the open issues in JIRA which have
been flagged as "newcomer":
https://issues.apache.org/jira/browse/DERBY/component/12310640

You might see something there which is interesting and suggests an initial
place to explore.

Another good thing to do is to verify that you can successfully build
the code from scratch and run all the regression tests. The Derby regression
suite is quite thorough, and you should be able to get a 100% pass rate.

Let us know of your progress!

bryan