From mboxrd@z Thu Jan 1 00:00:00 1970 From: Danny Milosavljevic Subject: bug#30644: Cuirass runs out of build users Date: Thu, 8 Mar 2018 01:29:23 +0100 Message-ID: <20180308012923.525342f6@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> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/nQe7m8nQMui2sph/kTmAvt9"; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44277) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1etjRf-0001eh-OC for bug-guix@gnu.org; Wed, 07 Mar 2018 19:30:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1etjRa-0000bZ-RD for bug-guix@gnu.org; Wed, 07 Mar 2018 19:30:07 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:42146) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1etjRa-0000bN-Na for bug-guix@gnu.org; Wed, 07 Mar 2018 19:30:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1etjRa-00009H-Ao for bug-guix@gnu.org; Wed, 07 Mar 2018 19:30:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20180308012541.517dc4dc@scratchpost.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_/nQe7m8nQMui2sph/kTmAvt9 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Oops, I had an old bin/evaluate . bin/evaluate.in doesn't contain it anymor= e. My bad... So please disregard. Anyway, sqlite contains some cool stuff to find out who's locking it. But as things are it seems that sqlite access is now done only by one threa= d. How can it then be locked? Weird... --Sig_/nQe7m8nQMui2sph/kTmAvt9 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAlqgg+MACgkQ5xo1VCww uqWkRwf/Xt2wnMO5jh6ePZIx30l7On4i+ZUhT5g79xA75xZpmlESb2Bi6ZgwaEIN qBIqHZIXUPlQISdgRl09XiGYIAtqH/lK/5GhTLWJn+hOYxSmPxcyEQkWP9leR+YQ hEO4ZV1dATMjt6NeNCqIR4/DxY5BRanm6hm6LCeqZvU80utVVEKgvqhfnhpMfEk9 D2ZtqrWarYN/B3dDaO7bIsKVpsYW5fwTEsvONUhKgCqB0KtuMvARbUjKvpKvAQuZ l/4B8e30rH+0Ba4rHAXUiArWG7LsQZ31FiJBGKkutwGPBlhs5tpJaRVdWKOYF7ee uQ9fRkvUHW5sCN4Y7oMv6IWu/KCBqA== =anV4 -----END PGP SIGNATURE----- --Sig_/nQe7m8nQMui2sph/kTmAvt9--