#2177: Trigger goes out to lunch and never comes back!
--------------------------+------------------------
Reporter: seb_kuzminsky | Owner:
Type: undecided | Status: new
Priority: major | Milestone: undecided
Version: 0.8.5 | Resolution:
Keywords: |
--------------------------+------------------------
Comment (by dustin):
Oh, I bet it's these:
{{{
sqlalchemy.exc.OperationalError: (OperationalError) database is
locked u'UPDATE buildrequests SET complete=?, results=?, complete_at=?
WHERE buildrequests.id IN (?) AND buildrequests.complete != ?' (1, 1,
1326476610.146077, 1895, 1)
}}}
where such an error would cause a buildrequest to not be marked complete.
Such a build request should eventually be run-run, but a failure to mark a
buildset as complete would not be fixed up later.
What version of sqlite are you using?
--
Ticket URL: <http://trac.buildbot.net/ticket/2177#comment:3>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
