Re: tests failing

On 06 Oct 2004 00:03:03 +0200, Sebastien Bigaret
<[email protected]> wrote:
>   Before this is fixed, you can have all the tests run w/ the procedure
>   described in the README: ./run.py (NO -g), plus the three
>   ./test_EditingContext_XXX.py scripts.
> 
> --> The four test script should give zero error & zero warning w/
>     0.9pre17.1 (this is part of the procedure rnu before every release)

ok, except for the encoding errors, this is true here also.

> > am I doing something wrong? I'm guessing the README is outdated,
> > because I tried that and it was even worse; I ran
> > 'test_EditingContext_Global.py -r' and
> > 'test_EditingContext_Global_Inheritance.py -r', and then 'run.py -g'.
> > These two give errors every time, complaining that
> >
> > DROP INDEX WRITER_pkey
> > error: Couldn't evaluate expression DROP INDEX WRITER_pkey. Reason:
> > psycopg.ProgrammingError:ERROR:  cannot drop index writer_pkey because
> > constraint writer_pkey on table writer requires it
> > HINT:  You may drop constraint writer_pkey on table writer instead.
> 
> Another bug here. Workaround: to regenerate the test databases, connect
> to the admin. db template1, then
> 
>     DROP DATABASE "AUTHOR_BOOKS";
>     CREATE DATABASE "AUTHOR_BOOKS";
>     DROP DATABASE "STORE_EMPLOYEES";
>     CREATE DATABASE "STORE_EMPLOYEES"

createdb -E LATIN1 AUTHOR_BOOKS; createdb -E LATIN1 STORE_EMPLOYEES

works fine too (on debian, at least).

> and finally run the scripts:
>     ./test_EditingContext_Global.py -r
>     ./test_EditingContext_Global_Inheritance.py -r
> 
> Your test-dbs should then be okay.
> 
> > Also, one thing that isn't mentioned in the README is that the
> > database must be created with -E LATIN1, or it will produce an(other)
> > error.
> 
> Third bug --could you be more explicit about the error? What is the
> default encoding you use, and how can I reproduce it here (an other -E
> option?) ?
> 
> If I may ask and I you have some time, could you submit bug reports
> @sf.net please?

now I know which are bugs in Modeling and not bungles in my setup, I will.

-- 
John Lenton ([email protected]) -- Random fortune:
bash: fortune: command not found


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl