On 24 Mar 2010, at 09:25, Benoit Chesneau wrote: > On Wed, Mar 24, 2010 at 5:18 PM, Jan Lehnardt <[email protected]> wrote: >> >> On 24 Mar 2010, at 02:44, Noah Slater wrote: >> >>> >>> On 24 Mar 2010, at 09:40, Brian Candler wrote: >>> >>>> Anyway, nobody else seems to have had this problem, it's quite possibly >>>> something to do with my setup, and browser-based tests are fragile anyway. >>>> Hence I'm not going to vote against the release. It's a 0 from me. >>> >>> Not true, you are the second to report it in this vote. >>> >>> Any of the developers (Jan?) want to comment on how serious this bug is? >> >> Brian, Benoit, can you both double check and do a clean-slate installation >> into a new --prefix if you haven't done so? >> >>> ** {{badmatch,{error,eacces}}, >> >> >> From Brian's stacktrace, I'm seeing the eaccess error which suggests that >> CouchDB doesn't have write permissions to local.ini (or local_dev.ini, if >> you run in make dev mode). >> >> -- >> >>> [Wed, 24 Mar 2010 09:00:50 GMT] [info] [<0.113.0>] OS Process #Port<0.1864> >>> Log :: function raised exception (new ReferenceError("map_funs is not >>> defined", "")) with doc._id 8450bfd7a0371f80a9baf032553367f4 >>> … >>> [Wed, 24 Mar 2010 09:00:50 GMT] [info] [<0.113.0>] OS Process #Port<0.1864> >>> Log :: function raised exception (new ReferenceError("map_results is not >>> defined", "")) with doc._id 8450bfd7a0371f80a9baf032553367f4 >> >> These come from the view server and look like there's a weird condition. >> Chris, maybe you can comment on this? >> >> Cheers >> Jan >> -- > like i said i redid install. alsso have the same error in dev mode. > Read my previous mail about it (more details in it if I remember). It > was really hard to have all tests ok yesterday. I will retry it later > tonight when i'm back at my office.
I only see > but on osx i had really bad times with js tests on ff 3.6/snow leopard > on my macbook. Sometimes changes tests where failing (due to io I > guess) and if you stop the tests they let the config in bad state > and it's not resetted in tests apparently, all tests were failing due > to auth. More info would be great :) Thanks Benoit. Cheers Jan --
