Michael go into python and type:
Michael from pysqlite2 import dbapi2
Michael dbapi2.sqlite_version
Well, that failed:
$ /tmp/python-buildbot/local/bin/python
Python 2.6a0 (trunk:54421, Mar 17 2007, 11:17:17)
[GCC 4.0.0 (Apple Computer, Inc. build 5026)] on darwin
yes 3.1.3 is a fairly old version (from February 2005), the unit
tests are assuming at least version 3.2.3 of sqlite. but youre best
off with the very latest 3.3.13.
On Mar 17, 2007, at 4:25 PM, [EMAIL PROTECTED] wrote:
Michael go into python and type:
Michael from pysqlite2
all tests pass on Mac OSX with the latest sqlite (as well as
postgres, mysql).
solaris, not so sure, ill have a look later.
On Mar 16, 2007, at 1:19 PM, [EMAIL PROTECTED] wrote:
Michael OK this was something small, the alltests.py scripts
needed
Michael to call testbase's
I just ran my python 2.5 install (its a framework install) on OSX
against the test suite on r2418, which uses the built-in sqlite3, and
i got all tests passed.
On Mar 16, 2007, at 1:19 PM, [EMAIL PROTECTED] wrote:
Michael OK this was something small, the alltests.py scripts
needed
geez, what version of sqlite / pysqlite / python is running there ?
tons of those errors ive never seen before.
On Mar 16, 2007, at 1:19 PM, [EMAIL PROTECTED] wrote:
Michael OK this was something small, the alltests.py scripts
needed
Michael to call testbase's main() function
ah, in fact one failure youre having, the testcast failure, is
indicative of running against a very old sqlite.
FAIL: testcast (sql.select.SelectTest)
--
Traceback (most recent call last):
File
Michael all tests pass on Mac OSX with the latest sqlite (as well as
Michael postgres, mysql).
Hmmm... Then I wonder what's different about the buildbot setup and a
normal interactive run.
Michael solaris, not so sure, ill have a look later.
There's no particular need. I was
Michael geez, what version of sqlite / pysqlite / python is running
Michael there ? tons of those errors ive never seen before.
That will have to wait for me to get home. Probably not until tomorrow at
the earliest. I'll let you know what I figure out. Perhaps I can tweak the
Michael ah, in fact one failure youre having, the testcast failure,
Michael is indicative of running against a very old sqlite.
Can you tell me what version I'm using other than very old? Here's what I
see:
$ otool -L lib-dynload/_sqlite3.so
lib-dynload/_sqlite3.so:
go into python and type:
from pysqlite2 import dbapi2
dbapi2.sqlite_version
On Mar 16, 2007, at 3:23 PM, [EMAIL PROTECTED] wrote:
Michael ah, in fact one failure youre having, the testcast
failure,
Michael is indicative of running against a very old sqlite.
Can you tell me
there is a sys.exit() that I added at Grig's request at the end of
testbase.py; its testbase.py's main() method that runs the actual
tests in all cases. the result code is determined by unittest's
result.wasSuccessful(). it was working when i first implemented it,
maybe you can help
OK this was something small, the alltests.py scripts needed to call
testbase's main() function and not its runTests() method, so that the
exit code is propigated. rev 2414.
On Mar 14, 2007, at 10:30 PM, [EMAIL PROTECTED] wrote:
Some of you may know that I run a Python buildbot for
Michael OK this was something small, the alltests.py scripts needed
Michael to call testbase's main() function and not its runTests()
Michael method, so that the exit code is propigated. rev 2414.
Excellent. Trying a test run now...
Skip
13 matches
Mail list logo
