From: Richard Purdie <richard.purdie@linuxfoundation.org>
Date: Wed, 24 Jul 2019 13:12:05 +0000 (+0100)
Subject: bitbake: prserv: Use a memory journal
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=94d5c61c9afd286e15f6ccd7b7b9e695bfcb0f97;p=thirdparty%2Fopenembedded%2Fopenembedded-core-contrib.git

bitbake: prserv: Use a memory journal

We've seen PR Server timeouts on the autobuilder, this is likely from the
journal being blocked on disk IO generated by the build.

Since we're running with synchronous off, we may as well put the journal
into memory and avoid any IO related stalls.

(Bitbake rev: ee3fc6030e653f3244b065fc89aafd2a7c36ae04)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---

diff --git a/bitbake/lib/prserv/db.py b/bitbake/lib/prserv/db.py
index d6188a679b7..117d8c052c1 100644
--- a/bitbake/lib/prserv/db.py
+++ b/bitbake/lib/prserv/db.py
@@ -257,7 +257,7 @@ class PRData(object):
         self.connection=sqlite3.connect(self.filename, isolation_level="EXCLUSIVE", check_same_thread = False)
         self.connection.row_factory=sqlite3.Row
         self.connection.execute("pragma synchronous = off;")
-        self.connection.execute("PRAGMA journal_mode = WAL;")
+        self.connection.execute("PRAGMA journal_mode = MEMORY;")
         self._tables={}
 
     def disconnect(self):