From mboxrd@z Thu Jan 1 00:00:00 1970 From: Danny Milosavljevic Subject: bug#30644: Cuirass runs out of build users Date: Sat, 24 Mar 2018 14:15:47 +0100 Message-ID: <20180324141547.109dc91a@scratchpost.org> References: <20180228090714.GA1845@jurong> <20180302140833.GB3213@macbook41> <20180305090256.GA9171@jurong> <20180305155351.GA6054@jurong> <87efkvpl8f.fsf@gnu.org> <20180308000111.77cce7d6@scratchpost.org> <20180308012541.517dc4dc@scratchpost.org> <20180308012923.525342f6@scratchpost.org> <87efkuojya.fsf@gnu.org> <20180311070610.788df5b9@scratchpost.org> <87zi3ethij.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_//dNy91vnMfpSmU+cSuwVBDa"; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48891) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ezlhK-0004Iv-T8 for bug-guix@gnu.org; Sat, 24 Mar 2018 12:08:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ezlYt-0007dW-76 for bug-guix@gnu.org; Sat, 24 Mar 2018 11:59:37 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:42657) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ezj1e-0007JG-3Q for bug-guix@gnu.org; Sat, 24 Mar 2018 09:16:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ezj1d-000700-Nq for bug-guix@gnu.org; Sat, 24 Mar 2018 09:16:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87zi3ethij.fsf@gnu.org> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 30644@debbugs.gnu.org --Sig_//dNy91vnMfpSmU+cSuwVBDa Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi Ludo, I've checked it some more. The shared cache uses unlock_notify, and the ac= tual database uses sqlite3_busy_handler (sqlite3_busy_timeout) when BUSY is retu= rned. The 5 in ice-9/eval.scm:619:8: Throw to key `sqlite-error' with args `(#f 5 "databas= e is locked")'. =20 ^^ means SQLITE_BUSY, so that's the actual database. So the easiest way to work around it would be to call sqlite3_busy_timeout(db, 10); // ms which would automatically repeatedly retry on busy until 10 ms have accumul= ated, and only then give up. There's also sqlite3_busy_handler which can be used to install a busy handl= er, and of course in the future we could also handle SQLITE_BUSY ourselves and = yield. See also https://notabug.org/civodul/guile-sqlite3/pulls/4 for the former. --Sig_//dNy91vnMfpSmU+cSuwVBDa Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAlq2T4MACgkQ5xo1VCww uqWRqQf+LFBG3nX4LDadOXErzJphQ51SV/z4UCEGWedLVhc58mlOnw7FDAcHyplU L2knIMYOUYoA5c+3muFaLfn43fsrwgUbQEYFBwVEDytyp57nCzr0iYv318A9YCgc rdIp5WruadE3nieHgBconum9aIw7/f6XNVKP6dULkv3gehdoo8VoVdLoW9+KUyig Fog72vQzblzkw+l0qqc1I64hYFalk6gmQLDyQAYrgYKzCQfP5TtO7W+QH7tPDKJs /po89CJG9LfUCQFxkZ6vH/upg4/RQaflzJxLrQK7YPGeAQshdJ9QNluvyvGXxSOe H8KDJ/jCiszWyNCo01BtRlidJNN2vg== =xJpK -----END PGP SIGNATURE----- --Sig_//dNy91vnMfpSmU+cSuwVBDa--