Hi David,>> Otherwise I''m fully committed to getting 0.10 out. >> When it is out, I''d recommend getting it into your >> development app as soon as you can.Any idea of timeframe to a 0.10 alpha release? Kind Regards Neville
Hi Neville,
It''s usable in subversion now. There are still a few little things I
have to add and a lot of documentation that I need to add. You can
check it out from;
svn co svn://www.davebalmain.com/exp
I''m going to try and get the gem out today. Give me 12 hours.
Cheers,
Dave
On 8/15/06, Neville Burnell <Neville.Burnell at bmsoft.com.au>
wrote:> Hi David,
>
> >> Otherwise I''m fully committed to getting 0.10 out.
> >> When it is out, I''d recommend getting it into your
> >> development app as soon as you can.
>
> Any idea of timeframe to a 0.10 alpha release?
>
> Kind Regards
>
> Neville
> _______________________________________________
> Ferret-talk mailing list
> Ferret-talk at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ferret-talk
>
> It''s usable in subversion now. There are still a few little things I > have to add and a lot of documentation that I need to add. You can > check it out from; > > svn co svn://www.davebalmain.com/exp > > I''m going to try and get the gem out today. Give me 12 hours.hey dave, is there some sort of a changelog? i see one in the trunk but its rather old.. would be nice to see what has changed :) Ben
I''ll try and list some of the changes when I announce it the release. I wasn''t able to keep a running change log because 0.10.0 is pretty much a rewrite. On 8/15/06, Benjamin Krause <bk at benjaminkrause.com> wrote:> > > It''s usable in subversion now. There are still a few little things I > > have to add and a lot of documentation that I need to add. You can > > check it out from; > > > > svn co svn://www.davebalmain.com/exp > > > > I''m going to try and get the gem out today. Give me 12 hours. > > hey dave, > > is there some sort of a changelog? i see one in the trunk but its rather > old.. would be nice to see what has changed :) > > Ben > > _______________________________________________ > Ferret-talk mailing list > Ferret-talk at rubyforge.org > http://rubyforge.org/mailman/listinfo/ferret-talk >
David Balmain wrote:> Hi Neville, > > It''s usable in subversion now. There are still a few little things I > have to add and a lot of documentation that I need to add. You can > check it out from; > > svn co svn://www.davebalmain.com/expI get a bus error with the C test (rev. 504): $ ./testall test_test : .SUCCESS test_global : .SUCCESS test_except : ....SUCCESS test_array : ....SUCCESS test_hash : .......SUCCESS test_hashset : ....SUCCESS test_bitvector : .........SUCCESS test_priorityqueue : ....SUCCESS test_helper : ...SUCCESS test_mem_pool : ...SUCCESS test_fs_store : ................SUCCESS test_ram_store : .................SUCCESS test_compound_io : ....SUCCESS test_fields : .......SUCCESS test_segments : ...SUCCESS test_document : ....SUCCESS test_analysis : ..F.F.|Bus error The Ruby test fails with this error: 1) Failure: test_boolean_query(SearcherTest) [./test/unit/search/tc_index_searcher.rb:39:in `check_hits'' ./test/unit/search/tm_searcher.rb:90:in `test_boolean_query'']: <14> expected but was <2>. -- Posted via http://www.ruby-forum.com/.
On 8/18/06, Andreas Schwarz <f at andreas-s.net> wrote:> David Balmain wrote: > > Hi Neville, > > > > It''s usable in subversion now. There are still a few little things I > > have to add and a lot of documentation that I need to add. You can > > check it out from; > > > > svn co svn://www.davebalmain.com/exp > > I get a bus error with the C test (rev. 504): > > $ ./testall > test_test : .SUCCESS > test_global : .SUCCESS > test_except : ....SUCCESS > test_array : ....SUCCESS > test_hash : .......SUCCESS > test_hashset : ....SUCCESS > test_bitvector : .........SUCCESS > test_priorityqueue : ....SUCCESS > test_helper : ...SUCCESS > test_mem_pool : ...SUCCESS > test_fs_store : ................SUCCESS > test_ram_store : .................SUCCESS > test_compound_io : ....SUCCESS > test_fields : .......SUCCESS > test_segments : ...SUCCESS > test_document : ....SUCCESS > test_analysis : ..F.F.|Bus error > > The Ruby test fails with this error: > > 1) Failure: > test_boolean_query(SearcherTest) > [./test/unit/search/tc_index_searcher.rb:39:in `check_hits'' > ./test/unit/search/tm_searcher.rb:90:in `test_boolean_query'']: > <14> expected but was > <2>.Hi Andreas, Thanks for running the tests. What kind of system are you running this on? Is it 64-bit or something? I finally released the 0.10.0 gem. If you have the time, could you try it? Cheers, Dave
David Balmain wrote:> On 8/18/06, Andreas Schwarz <f at andreas-s.net> wrote: >> >> test_mem_pool : ...SUCCESS >> 1) Failure: >> test_boolean_query(SearcherTest) >> [./test/unit/search/tc_index_searcher.rb:39:in `check_hits'' >> ./test/unit/search/tm_searcher.rb:90:in `test_boolean_query'']: >> <14> expected but was >> <2>. > > > Hi Andreas, > > Thanks for running the tests. What kind of system are you running this > on? Is it 64-bit or something?OS X 10.4 on PowerPC G4. I''ll try on Linux i686 later.> I finally released the 0.10.0 gem. If > you have the time, could you try it?I just tried Rev. 511. Still the same Bus error as above, still the same test_boolean_query failure, and a few more: 1) Failure: test_custom_filter(CustomAnalyzerTest) [./test/unit/../unit/utils/../../unit/index/../../unit/query_parser/../../unit/search/../../unit/store/../../unit/analysis/tc_analyzer.rb:502]: <token["dbalm??n at gmail.com":0:18:1]> expected but was <token["dbalm":0:5:1]>. 2) Failure: test_c_letter_analyzer(LetterAnalyzerTest) [./test/unit/../unit/utils/../../unit/index/../../unit/query_parser/../../unit/search/../../unit/store/../../unit/analysis/tc_analyzer.rb:92]: <token["DBalm??n":0:8:1]> expected but was <token["DBalm":0:5:1]>. 3) Failure: test_letter_tokenizer(LetterTokenizerTest) [./test/unit/../unit/utils/../../unit/index/../../unit/query_parser/../../unit/search/../../unit/store/../../unit/analysis/tc_token_stream.rb:64]: <token["DBalm??n":0:8:1]> expected but was <token["DBalm":0:5:1]>. 4) Failure: test_sorts(SearchAndSortTest) [./test/unit/../unit/utils/../../unit/index/../../unit/query_parser/../../unit/search/tc_search_and_sort.rb:40:in `do_test_top_docs'' ./test/unit/../unit/utils/../../unit/index/../../unit/query_parser/../../unit/search/tc_search_and_sort.rb:39:in `do_test_top_docs'' ./test/unit/../unit/utils/../../unit/index/../../unit/query_parser/../../unit/search/tc_search_and_sort.rb:113:in `test_sorts'']: <8> expected but was <1>. 5) Failure: test_boolean_query(SearcherTest) [./test/unit/../unit/utils/../../unit/index/../../unit/query_parser/../../unit/search/tc_index_searcher.rb:39:in `check_hits'' ./test/unit/../unit/utils/../../unit/index/../../unit/query_parser/../../unit/search/tm_searcher.rb:90:in `test_boolean_query'']: <14> expected but was <2>. 6) Failure: test_boolean_query(SimpleMultiSearcherTest) [./test/unit/../unit/utils/../../unit/index/../../unit/query_parser/../../unit/search/tc_index_searcher.rb:39:in `check_hits'' ./test/unit/../unit/utils/../../unit/index/../../unit/query_parser/../../unit/search/tm_searcher.rb:90:in `test_boolean_query'']: <14> expected but was <2>. 7) Failure: test_c_standard_analyzer(StandardAnalyzerTest) [./test/unit/../unit/utils/../../unit/index/../../unit/query_parser/../../unit/search/../../unit/store/../../unit/analysis/tc_analyzer.rb:269]: <token["dbalm??n at gmail.com":0:18:1]> expected but was <token["dbalm":0:5:1]>. 8) Failure: test_standard_tokenizer(StandardTokenizerTest) [./test/unit/../unit/utils/../../unit/index/../../unit/query_parser/../../unit/search/../../unit/store/../../unit/analysis/tc_token_stream.rb:232]: <token["DBalm??n at gmail.com":0:18:1]> expected but was <token["DBalm":0:5:1]>. 9) Failure: test_stop_filter(StemFilterTest) [./test/unit/../unit/utils/../../unit/index/../../unit/query_parser/../../unit/search/../../unit/store/../../unit/analysis/tc_token_stream.rb:402]: <token["d??bate":0:7:1]> expected but was <token["d":0:1:1]>. 10) Failure: test_c_white_space_analyzer(WhiteSpaceAnalyzerTest) [./test/unit/../unit/utils/../../unit/index/../../unit/query_parser/../../unit/search/../../unit/store/../../unit/analysis/tc_analyzer.rb:214]: <token["????g??????????????????????????":55:86:1]> expected but was <token["??g????????????????":55:86:1]>. 11) Failure: test_whitespace_tokenizer(WhiteSpaceTokenizerTest) [./test/unit/../unit/utils/../../unit/index/../../unit/query_parser/../../unit/search/../../unit/store/../../unit/analysis/tc_token_stream.rb:174]: <token["????g??????????????????????????":55:86:1]> expected but was <token["??g????????????????":55:86:1]>. -- Posted via http://www.ruby-forum.com/.
Andreas Schwarz wrote:> David Balmain wrote: >> On 8/18/06, Andreas Schwarz <f at andreas-s.net> wrote: >>> >>> test_mem_pool : ...SUCCESS >>> 1) Failure: >>> test_boolean_query(SearcherTest) >>> [./test/unit/search/tc_index_searcher.rb:39:in `check_hits'' >>> ./test/unit/search/tm_searcher.rb:90:in `test_boolean_query'']: >>> <14> expected but was >>> <2>. >> >> >> Hi Andreas, >> >> Thanks for running the tests. What kind of system are you running this >> on? Is it 64-bit or something? > > OS X 10.4 on PowerPC G4. I''ll try on Linux i686 later.OK, tried it on Debian Sarge, i686. First a minor problem: gcc-3.3 doesn''t know -Wextra, I had to remove it from the Makefile. In the C test I get the equivalent of the Bus Error: $ ./testall test_test : .SUCCESS test_global : .SUCCESS test_except : ....SUCCESS test_array : ....SUCCESS test_hash : .......SUCCESS test_hashset : ....SUCCESS test_bitvector : .........SUCCESS test_priorityqueue : ....SUCCESS test_helper : ...SUCCESS test_mem_pool : ...SUCCESS test_fs_store : ................SUCCESS test_ram_store : .................SUCCESS test_compound_io : ....SUCCESS test_fields : .......SUCCESS test_segments : ...SUCCESS test_document : ....SUCCESS test_analysis : ..F.F.\Segmentation fault The first time I ran the ruby test it hung with 100% CPU usage after about 15 tests and I had to kill -9 it, the second time it started spamming my console with "?:502: [BUG] ?:502: [BUG] ?:502: [BUG] ?:502: [BUG] ?:502: [BUG] ?:502:" at the same point. -- Posted via http://www.ruby-forum.com/.
On 8/23/06, Andreas Schwarz <f at andreas-s.net> wrote:> Andreas Schwarz wrote: > > David Balmain wrote: > >> On 8/18/06, Andreas Schwarz <f at andreas-s.net> wrote: > >>> > >>> test_mem_pool : ...SUCCESS > >>> 1) Failure: > >>> test_boolean_query(SearcherTest) > >>> [./test/unit/search/tc_index_searcher.rb:39:in `check_hits'' > >>> ./test/unit/search/tm_searcher.rb:90:in `test_boolean_query'']: > >>> <14> expected but was > >>> <2>. > >> > >> > >> Hi Andreas, > >> > >> Thanks for running the tests. What kind of system are you running this > >> on? Is it 64-bit or something? > > > > OS X 10.4 on PowerPC G4. I''ll try on Linux i686 later. > > OK, tried it on Debian Sarge, i686. First a minor problem: gcc-3.3 > doesn''t know -Wextra, I had to remove it from the Makefile. > > In the C test I get the equivalent of the Bus Error: > $ ./testall > test_test : .SUCCESS > test_global : .SUCCESS > test_except : ....SUCCESS > test_array : ....SUCCESS > test_hash : .......SUCCESS > test_hashset : ....SUCCESS > test_bitvector : .........SUCCESS > test_priorityqueue : ....SUCCESS > test_helper : ...SUCCESS > test_mem_pool : ...SUCCESS > test_fs_store : ................SUCCESS > test_ram_store : .................SUCCESS > test_compound_io : ....SUCCESS > test_fields : .......SUCCESS > test_segments : ...SUCCESS > test_document : ....SUCCESS > test_analysis : ..F.F.\Segmentation fault > > The first time I ran the ruby test it hung with 100% CPU usage after > about 15 tests and I had to kill -9 it, the second time it started > spamming my console with "?:502: [BUG] ?:502: [BUG] ?:502: [BUG] ?:502: > [BUG] ?:502: [BUG] ?:502:" at the same point.Hi Andreas, It seems like most of those ruby tests are failing because the default locale doesn''t handle UTF-8. This shouldn''t be too hard to fix. A couple of the errors are worrying though and I''d love to find out what is causing the segmentation fault. I don''t suppose you could get me a ssh login on that Sarge machine for few hours? I''m not holding my breath but it''d certainly speed things up a bit. Cheers, Dave