summaryrefslogtreecommitdiffstats
path: root/bitbake/lib
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2014-05-03 11:18:33 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2014-05-03 11:24:48 +0100
commit99c9b337ac0c33870bf0240d2b348047a712a83c (patch)
tree69dbd3058b9d1c0bfd51659e242c239e794bcc7d /bitbake/lib
parentc1f4df4e883c3e03f561071390d8a204240f069a (diff)
downloadpoky-99c9b337ac0c33870bf0240d2b348047a712a83c.tar.gz
bitbake: persist_data: Avoid fsync() calls
If the power were to fail, it doesn't matter to us much if the data makes it to disk or not, we'd have other problems. However an fsync() call on a multi build autobuilder is painful so lets avoid them. This is particularly true in this case if a timeout causes a reconnect during a build. (Bitbake rev: ec28256ac2a30f047585e8f61200d764bc295ded) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib')
-rw-r--r--bitbake/lib/bb/persist_data.py4
1 files changed, 3 insertions, 1 deletions
diff --git a/bitbake/lib/bb/persist_data.py b/bitbake/lib/bb/persist_data.py
index 994e61b0a6..5795bc835b 100644
--- a/bitbake/lib/bb/persist_data.py
+++ b/bitbake/lib/bb/persist_data.py
@@ -199,7 +199,9 @@ class PersistData(object):
199 del self.data[domain][key] 199 del self.data[domain][key]
200 200
201def connect(database): 201def connect(database):
202 return sqlite3.connect(database, timeout=5, isolation_level=None) 202 connection = sqlite3.connect(database, timeout=5, isolation_level=None)
203 connection.execute("pragma synchronous = off;")
204 return connection
203 205
204def persist(domain, d): 206def persist(domain, d):
205 """Convenience factory for SQLTable objects based upon metadata""" 207 """Convenience factory for SQLTable objects based upon metadata"""