Mercurial > p > roundup > code
view website/issues/html/home.classlist.html @ 5142:93832cec4c31
issue2550839: Xapian, DatabaseLockError: Unable to get write lock on
db/text-index: already locked
I put in a retry loop that will attempt to get the lock. 10 tries with
a delaythatvaries from .02 seconds to .64 seconds. Total delay over 10
cycles approx. 4.5 seconds.
I can't figure out how to make pytest run two parallel processes to
test this code. I did try running:
./run_tests.py -k Xapian test/test_indexer.py &
./run_tests.py -k Xapian test/test_indexer.py
and confirmed that one of the processes seemed to hang on a test and
then threw a lock failure error. So at least the code path is being
exercised.
If anybody knows how to correctly test this I would love to do a real
test.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Wed, 13 Jul 2016 19:42:44 -0400 |
| parents | c2d0d3e9099d |
| children |
line wrap: on
line source
<tal:block metal:use-macro="templates/page/macros/icing"> <title metal:fill-slot="head_title" i18n:translate="">List of classes - <span i18n:name="tracker" tal:replace="config/TRACKER_NAME" /></title> <span metal:fill-slot="body_title" tal:omit-tag="python:1" i18n:translate="">List of classes</span> <td class="content" metal:fill-slot="content"> <table class="classlist"> <tal:block tal:repeat="cl db/classes"> <tr> <th class="header" colspan="2" align="left"> <a tal:attributes="href string:${cl/classname}" tal:content="python:cl.classname.capitalize()">classname</a> </th> </tr> <tr tal:repeat="prop cl/properties"> <th tal:content="prop/_name">name</th> <td tal:content="prop/_prop">type</td> </tr> </tal:block> </table> </td> </tal:block>
