Hi Chris, I've retried my tests and they all passed successfully :)
Now I think of it, could it be because the ucla server was so busy with the megatests that it timed out when I tried to connect? I was planning on checking the MySQLdb/connections.py and changing the time-out setting to a longer waiting period, so that the server will not give up the connection so quickly. jenny On Tue, Oct 21, 2008 at 9:07 PM, Christopher Lee <[EMAIL PROTECTED]> wrote: > > Hi Jenny, > looks like the SQL server is not responding to your connection > request. There haven't been any pygr code changes affecting this > sqlgraph functionality lately, and all the SQL / mysql tests in the > test suite pass fine with the latest code. > > Can you retry your tests, or verify that you can connect to the mysql > server by hand (i.e. with the command line mysql client)? > > Yours with best wishes, > > -- Chris > On Oct 20, 2008, at 11:56 PM, Jenny Qing Qian wrote: > > > > > File "/home/qing/workspace2008/pygr_new/pygr/pygr/ > > sqlgraph.py", line 1399, in cursor > > self._cursor = connect(**self.kwargs).cursor() > > File "/var/lib/python-support/python2.5/MySQLdb/__init__.py", > > line 74, in Connect > > return Connection(*args, **kwargs) > > File "/var/lib/python-support/python2.5/MySQLdb/ > > connections.py", line 170, in __init__ > > super(Connection, self).__init__(*args, **kwargs2) > > OperationalError: (2013, "Lost connection to MySQL server at > > 'reading authorization packet', system error: 0") > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
