OK i cant tell exactly what happened, but one major gotcha with these unittests is that they all run with the same database connection all the way through. so if it trips up really bad on a few tests, it can sometimes throw the DB out of whack (usually by leaving a table present that was supposed to be removed), which causes subsequent tests to not create/delete their tables properly, and everything blows up. most of the errors here seem to be focusing on the "users" and "email_addresses" table not getting created.
so the strategy is then to run the test suites more specifically, i.e. test/orm/alltests.py to run just the ORM suite, test/ext/ activemapper.py to run just activemapper, etc. On Jul 1, 2006, at 12:34 AM, Charles Duffy wrote: > Michael Bayer wrote: >> tell me about the test suite. which tests are you running ? >> whats the command line youre trying ? > > This is at my office; I can't reproduce it at home, which is > leading me to wonder if it's an issue with the sqlite installed > there (3.3.4) or some other dependency. > > I'm running "python2.4 test/alltests.py --db=sqlite"; the end > result is 7 failures and 147 errors. Bzip2'd output is attached. > <sqlalchemy-test_results-verbose.bz2> Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
