incubator-gora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mattmann, Chris A (388J)" <chris.a.mattm...@jpl.nasa.gov>
Subject Re: [VOTE] Apache Gora 0.1-incubating release
Date Thu, 24 Feb 2011 16:40:47 GMT
+1 Julien, let's get the release moving with the functionality that it currently has. Several
major OS vendors have released their products to the world with 10s of K of known bugs --
releasing Gora with some limitations, but with the existing working functionality is just
fine.

Cheers,
Chris

On Feb 24, 2011, at 8:17 AM, Julien Nioche wrote:

> The trouble is that the tests for gora-hbase aren't working either. Can't find the exact
reason, I suspect it has to do with embedded HBase server or something like that.
> I think this should not prevent us from committing 0.1-incubating; gora-cassandra does
not have any tests anyway + what we really need is to get this first version out so that people
can start using it with Nutch 2.0 and find plenty of bugs :-)
> 
> We should definitely keep the test code for gora-hbase but add 
> 
>   <!-- do nothing for now as the tests need fixing -->
>   <target name="test" depends="compile-test" description="Run core unit tests"/>
> 
> to gora-hbase/build.xml to bypass the tests.
> 
> Julien
> 
> 
> On 24 February 2011 15:55, Mattmann, Chris A (388J) <chris.a.mattmann@jpl.nasa.gov>
wrote:
> Hi Guys,
> 
> Why don't we disable TestMemStore (since it never worked), and just roll forward with
the release? I don't think tests should block a release, especially since a few of them never
worked. That's the point of iterative development -- we can fix these or deal with them as
needed and desired by our users in 0.2(-incubating). We know that 0.1-incubating can ship
with whatever is working on, and then we'll get to whatever we didn't get to in 0.1-incubating
in the next release.
> 
> I'm +1 for Julien's suggestions below and for Henry to roll RC2.
> 
> Cheers,
> Chris
> 
> 
> On Feb 24, 2011, at 7:29 AM, Julien Nioche wrote:
> 
> > There were issues with gora-cassandra (and the other dependencies) but this
> > can be fixed by cleaning the ivy cache as Henry pointed out. For some reason
> > the deps were trying to use the version 0.1 instead of 0.1-incubating, and
> > the former had no 'test' configuration. My guess is that
> > 'latest.integration' which is used in the ivy files treated 0.1 as more
> > recent than 0.1-incubating (which in a way makes sense).
> >
> > The problem is now that we get 2 test failures in gora-core
> > (TestDataFileAvroStoreMapReduce and TestMemStore). The first one can be
> > fixed by simply adding
> >    <dependency org="org.slf4j" name="slf4j-simple" rev="1.5.8" conf="test
> > -> *,!sources,!javadoc"/>
> > to gora-core/ivy/ivy.xml
> >
> >
> > As for the TestMemStore, I don't think that this has ever worked. IIRC the
> > Memstore was meant to be used for testing only but is of little practical
> > use, its code would need to be fixed. I suggest that we either just remove
> > the test class for it or go one step further and remove the test and the
> > whole o.a.gora.memory package. There aren't many of us involved in this
> > project so I don't think we can afford to spend much time fixing things that
> > are not really needed and should rather focus on getting the basics right.
> >
> > Any views on that?
> >
> > Julien
> >
> >
> > On 21 February 2011 05:02, Henry Saputra <henry.saputra@gmail.com> wrote:
> >
> >> Hey Chris,
> >>
> >> There is a test failure in gora-cassandra. I have been trying out to
> >> figure out what went wrong but not too sure about the output from ivy.
> >>
> >> Any help is appreciated.
> >>
> >> Just run "ant test"
> >>
> >>
> >> - Henry
> >>
> >> On Sun, Feb 20, 2011 at 8:41 PM, Mattmann, Chris A (388J)
> >> <chris.a.mattmann@jpl.nasa.gov> wrote:
> >>> Hey Henry,
> >>>
> >>> Are you going to have time to roll RC2 this week?
> >>>
> >>> Thanks for your hard work!
> >>>
> >>> Cheers,
> >>> Chris
> >>>
> >>> On Feb 11, 2011, at 10:02 PM, Henry Saputra wrote:
> >>>
> >>>> Looks like ivy somehow messed up the timestamp for local copy for
> >>>> gora-core 0.1 and 0.1-incubating. Not exactly sure what happened her.
> >>>>
> >>>> However, you can bypass this error by deleting local and cache
> >>>> directories under ~/.ivy2.
> >>>>
> >>>> After I did it, I passed the missing library error and saw test fail
> >>>> and error in org.apache.gora.memory.store.TestMemStore:
> >>>>
> >>>> compile-test:
> >>>>
> >>>> test:
> >>>>  [delete] Deleting directory
> >>>> /Users/hsaputra/gora/branches/0.1-incubating/gora-core/build/test/data
> >>>>   [mkdir] Created dir:
> >>>> /Users/hsaputra/gora/branches/0.1-incubating/gora-core/build/test/data
> >>>>  [delete] Deleting directory
> >>>> /Users/hsaputra/gora/branches/0.1-incubating/gora-core/build/test/logs
> >>>>   [mkdir] Created dir:
> >>>> /Users/hsaputra/gora/branches/0.1-incubating/gora-core/build/test/logs
> >>>>   [junit] WARNING: multiple versions of ant detected in path for junit
> >>>>   [junit]
> >>>> jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/Project.class
> >>>>   [junit]      and
> >>>>
> >> jar:file:/Users/hsaputra/gora/branches/0.1-incubating/gora-core/lib/ant-1.6.5.jar!/org/apache/tools/ant/Project.class
> >>>>   [junit] Running org.apache.gora.avro.TestPersistentDatumReader
> >>>>   [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.484
sec
> >>>>   [junit] Running
> >>>> org.apache.gora.avro.mapreduce.TestDataFileAvroStoreMapReduce
> >>>>   [junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 79.674
> >> sec
> >>>>   [junit] Test
> >>>> org.apache.gora.avro.mapreduce.TestDataFileAvroStoreMapReduce FAILED
> >>>>   [junit] Running org.apache.gora.avro.store.TestAvroStore
> >>>>   [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 1.325
sec
> >>>>   [junit] Running org.apache.gora.avro.store.TestDataFileAvroStore
> >>>>   [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 1.557
sec
> >>>>   [junit] Running org.apache.gora.mapreduce.TestGoraInputFormat
> >>>>   [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.719
sec
> >>>>   [junit] Running org.apache.gora.mapreduce.TestGoraInputSplit
> >>>>   [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.548
sec
> >>>>   [junit] Running org.apache.gora.mapreduce.TestPersistentSerialization
> >>>>   [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.649
sec
> >>>>   [junit] Running org.apache.gora.memory.store.TestMemStore
> >>>>   [junit] Tests run: 28, Failures: 1, Errors: 6, Time elapsed: 0.493
> >> sec
> >>>>   [junit] Test org.apache.gora.memory.store.TestMemStore FAILED
> >>>>   [junit] Running org.apache.gora.persistency.impl.TestPersistentBase
> >>>>   [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 0.453
sec
> >>>>   [junit] Running org.apache.gora.persistency.impl.TestStateManagerImpl
> >>>>   [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 0.394
sec
> >>>>   [junit] Running org.apache.gora.query.impl.TestPartitionQueryImpl
> >>>>   [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.522
sec
> >>>>   [junit] Running org.apache.gora.query.impl.TestQueryBase
> >>>>   [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.599
sec
> >>>>   [junit] Running org.apache.gora.store.TestDataStoreFactory
> >>>>   [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 0.461
sec
> >>>>   [junit] Running org.apache.gora.util.TestIOUtils
> >>>>   [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 0.397
sec
> >>>>
> >>>> Trying to figure out which test cases cause the fail and errors.
> >>>>
> >>>> - Henry
> >>>>
> >>>> On Mon, Feb 7, 2011 at 7:43 AM, Andrzej Bialecki <ab@getopt.org>
wrote:
> >>>>> On 2/7/11 1:05 PM, Julien Nioche wrote:
> >>>>>>
> >>>>>> OK, I've changed my mind :-) Better to release 0.1 now and do
GORA-22
> >> in
> >>>>>> 0.2
> >>>>>> We'll maybe hear more details about the limitations / bugs of
the
> >> current
> >>>>>> implementation from Enis/Dogacan in the meantime + add more
features
> >> to
> >>>>>> GORA-22. Having 0.1 released and published is very important
for Nutch
> >> so
> >>>>>> +1
> >>>>>> from me
> >>>>>
> >>>>> I'm getting these during build:
> >>>>>
> >>>>> [ivy:resolve] :: problems summary ::
> >>>>> [ivy:resolve] :::: ERRORS
> >>>>> [ivy:resolve]   unknown resolver public
> >>>>> [ivy:resolve]   unknown resolver main
> >>>>>
> >>>>> The default target (publish-local-all) appears to finish ok, but
test
> >>>>> doesn't work - it bombs out with the following:
> >>>>>
> >>>>> ivy:resolve] :: problems summary ::
> >>>>> [ivy:resolve] :::: WARNINGS
> >>>>> [ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
> >>>>> [ivy:resolve]           ::          UNRESOLVED DEPENDENCIES    
    ::
> >>>>> [ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
> >>>>> [ivy:resolve]           :: org.apache.gora#gora-core;0.1: configuration
> >> not
> >>>>> found in org.apache.gora#gora-core;0.1: 'test'. It was required
from
> >>>>> org.apache.gora#gora-cassandra;working@abacus.local test
> >>>>> [ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
> >>>>> [ivy:resolve]
> >>>>> [ivy:resolve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
> >>>>>
> >>>>> BUILD FAILED
> >>>>> /Users/ab/work/gora/svn/branches/0.1-incubating/build.xml:278: The
> >> following
> >>>>> error occurred while executing this line:
> >>>>> /Users/ab/work/gora/svn/branches/0.1-incubating/build-common.xml:365:
> >>>>> impossible to resolve dependencies:
> >>>>>       resolve failed - see output for details
> >>>>>
> >>>>>
> >>>>> If there is some setup needed that I missed, IMHO it should be
> >> described in
> >>>>> the README. My env: Mac OSX 10.6.6, JDK 1.6.0_22 64-bit, Ant 1.8.1.
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Best regards,
> >>>>> Andrzej Bialecki     <><
> >>>>> ___. ___ ___ ___ _ _   __________________________________
> >>>>> [__ || __|__/|__||\/|  Information Retrieval, Semantic Web
> >>>>> ___|||__||  \|  ||  |  Embedded Unix, System Integration
> >>>>> http://www.sigram.com  Contact: info at sigram dot com
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Thanks,
> >>>> Henry
> >>>
> >>>
> >>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>> Chris Mattmann, Ph.D.
> >>> Senior Computer Scientist
> >>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> >>> Office: 171-266B, Mailstop: 171-246
> >>> Email: chris.a.mattmann@nasa.gov
> >>> WWW:   http://sunset.usc.edu/~mattmann/
> >>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>> Adjunct Assistant Professor, Computer Science Department
> >>> University of Southern California, Los Angeles, CA 90089 USA
> >>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>>
> >>>
> >>
> >>
> >>
> >> --
> >> Thanks,
> >> Henry
> >>
> >
> >
> >
> > --
> > *
> > *Open Source Solutions for Text Engineering
> >
> > http://digitalpebble.blogspot.com/
> > http://www.digitalpebble.com
> 
> 
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW:   http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 
> 
> 
> 
> -- 
> 
> Open Source Solutions for Text Engineering
> 
> http://digitalpebble.blogspot.com/
> http://www.digitalpebble.com


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Mime
View raw message