[Mailman-Users] MM3 Test "" Hangs

Stephen J. Turnbull stephen at xemacs.org
Wed Feb 26 06:45:53 CET 2014

Tom Browder writes:

We really appreciate your efforts to test the betas of Mailman 3.  But
please do be aware that although there are sites already successfully
using Mailman 3 in production, the development team doesn't recommend
use of any of the components (core, Postorius, HyperKitty) in
production yet.

 > I have no idea what to do next,

Nothing. :-)  I've already Cc'd (and set Reply-To to) mailman-developers,
which is a more appropriate place for this report.  (Many Mailman-Users
are not interested in MM3 yet, while Mailman-Developers are by
definition, as MM2 is basically end-of-life.  Also, some relevant
developers may read mailman-developers more frequently than they read

Actually, I do have a couple of ideas.  First, you should always
report the whole error trace (if you think that's ugly in an email,
attach it as a file).  In this particular case, I suspect that the
problem is in the test before the one that caused the Exception, which
failed leaving the database locked.  It would be very helpful to
identify that test, which would probably be the *first* frame in the

Second, you should look in the server's logs to see if there were any
errors that might have caused the incomplete transaction.

 > and help or ideas would be greatly appreciated. 

If you have no idea, then reporting to the developers is the best you
can do.  Use "Mailman Developers" <mailman-developers at python.org> or
report via Launchpad.

Pretty clearly what's happened is that some previous test locked the
database (probably anything that accesses the database does so at
least long enough to read the whole record), and either (1) that test
failed to unlock the database, (2) the test framework failed to unlock
the database, or (3) the tests were improperly sequenced in some way
and the database didn't get unlocked.  It's quite possible that this
failure could never be replicated in actual use, as tests often mock
up some component that would normally ensure that any pending
transaction gets discarded and the database unlocked.

Unfortunately I don't have an up-to-date test installation (it's on my
list for early next week), and looking at the test file doesn't tell
me anything.  Perhaps Barry has an idea for a fix, or a workaround.
And there's probably a way to skip that test, but I don't know nose
very well.


Original report follows:

 > i have started investigating MM3 for my new, remote server and
 > branched from lp:mailman, lp:postorius, and lp:hyperkitty.
 > I started in the MM3 branch directory and followed instructions in
 > src/mailman/docs/START.rst.
 > I got the virtualenv ready to go and, in the local mailman branch
 > directory, I executed:
 >   $  node2 -v
 > All tests chug along nicely until:
 >   /usr/local/src/0-mailman3/src/mailman/rest/docs/membership.rst ...
 > and it hangs longer than I think it should.  After a <ctl-C> the last
 > few trace-back lines are:
 >   File "/home/virtualenvs/mm3/local/lib/python2.7/site-packages/storm-0.20-py2.7-linux-i686.egg/storm/database.py",
 > line 374, in raw_execute
 >     self._run_execution(raw_cursor, args, params, statement)
 >   File "/home/virtualenvs/mm3/local/lib/python2.7/site-packages/storm-0.20-py2.7-linux-i686.egg/storm/database.py",
 > line 388, in _run_execution
 >     self._check_disconnect(raw_cursor.execute, *args)
 >   File "/home/virtualenvs/mm3/local/lib/python2.7/site-packages/storm-0.20-py2.7-linux-i686.egg/storm/database.py",
 > line 454, in _check_disconnect
 >     return function(*args, **kwargs)
 > sqlite3.OperationalError: database is locked
 > Note I am running the MM3 installation, via ssh, on a remote host
 > running Debian 7, 32-bit. (Note also postfix is running.)

More information about the Mailman-Users mailing list