From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS11403 66.111.4.0/24 X-Spam-Status: No, score=-3.9 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS, SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 4ACFA1F4BD for ; Wed, 2 Oct 2019 23:23:46 +0000 (UTC) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id A42D721B62; Wed, 2 Oct 2019 19:23:45 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Wed, 02 Oct 2019 19:23:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alyssa.is; h= from:to:cc:subject:in-reply-to:references:date:message-id :mime-version:content-type; s=fm1; bh=QvoMS4fyEsjA+0h7gXyFm3iwC1 B0yCqTZ5bHjMxHfco=; b=J31/zGBmj0sU3MKMEc31UbLuVQi1AA6etmCUQ/tOm6 2pfq91XhdAbz8KwwgLjC0JgEkYz0qcu2a+CGfxLuX3wVMpjRooIh3EOCCM1WqoFv nBiE+b7rADxouXSATXG8CHGe4IkA1Rzl5TnmFPJ1P9AXCBq8Wqr8SxCUG8iZcQkI sn14WJN4ouxiKRN3hjbp3ZV1L3u9P4UAvMi1D2ss0aWk6tfZDTeacpFpsX52RRWh onUSz1l60Tz/45jZQugQCFct131t+Eom7dCrqFf1Us8oT8Q4Mx0fHWcTMGXbHbx4 kJfnLTzLVBtafabibX1/QVVhYuK27uCjRlbaWLjwN8/g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=QvoMS4 fyEsjA+0h7gXyFm3iwC1B0yCqTZ5bHjMxHfco=; b=Xx93owB2xbwGjorWjz/iex ALeS8zXOck872NBGOL1g7u/51P/aRS7RHyrB6nRt+nJYDg0DFPVAZ2A1jlxVdE7a oq9LFctQl0QJpewG4sers02X+bKZqWK10fSfxfqUvE4C+fUlJ9mFt0S1bAkZnqh2 Wk1h44QdeGOAOyPE7ppn6Zav5Aim/VKWDF4Gp+IQ8Cng2SED9sW1tuZkLFOXif3q St2dy6hpbqOSWYGNN0+aNCk1Q8Yi3fBbORXbRx41xbNlOMXf7Xd2RMBio7gMsRTt sjhsx1R0HQ/+/Yk1mqwVbDU2erN9pW9TAuPTcfh+x+evoHGXg+w6MqrlBcvuRZYw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrgeejgddulecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhephffvufgjfhffkfggtgesghdtreertd dttdenucfhrhhomheptehlhihsshgrucftohhsshcuoehhihesrghlhihsshgrrdhisheq necukfhppeekgedrudekgedrvddvgedrudehtdenucfrrghrrghmpehmrghilhhfrhhomh ephhhisegrlhihshhsrgdrihhsnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from localhost (p54b8e096.dip0.t-ipconnect.de [84.184.224.150]) by mail.messagingengine.com (Postfix) with ESMTPA id 2A1E48005A; Wed, 2 Oct 2019 19:23:45 -0400 (EDT) From: Alyssa Ross To: Eric Wong Cc: meta@public-inbox.org Subject: Re: Test failures in build sandbox In-Reply-To: <20190926084431.ukv53sfskk7qvere@dcvr> References: <20190915134819.1406-1-hi@alyssa.is> <20190915185519.GA4891@dcvr> <87zhiu4hxl.fsf@alyssa.is> <20190924040123.6jbtvpadnk6negox@whir> <87r245tkbz.fsf@alyssa.is> <20190926084431.ukv53sfskk7qvere@dcvr> Date: Wed, 02 Oct 2019 23:23:39 +0000 Message-ID: <87bluyhguc.fsf@alyssa.is> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" List-Id: --=-=-= Content-Type: text/plain > What kind of filesystem and mount options was the code and > (if set, TMPDIR) on? > Since Nix seems to use odd paths, what's the default temporary > directory? ("/tmp" on my systems) TMPDIR is /build. The code is extracted to /build/public-inbox. Relevant mount output is: tmp on /build type tmpfs (rw,relatime) >> t/search.t ................. fatal: Could not make /build/pi-search-i646IK/a.git/branches/ writable by group >> t/search.t ................. 1/? >> # Failed test 'git init (main)' >> # at t/search.t line 20. >> # got: '0' >> # expected: '32768' After some rather extensive debugging, I've determined that most of these are to do with not being able to set the setgid bit. If I mask it off in git's adjust_shared_perm function, I get down to two failures. I don't know enough about filesystem permissions to know why this wouldn't be allowed inside the sandbox if it is allowed normally, though. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEH9wgcxqlHM/ARR3h+dvtSFmyccAFAl2VMXsACgkQ+dvtSFmy ccBSDg/9Hy0tB3d+3/dU3M0mEOGBil28CA9vnKFGzXl5mFGyvr34X7R7z3PX3JJd 5U6gDc1Ca+Hm7dn8IL2us2H5ElFwjmlkZste4uVwbYH1APJphXCfxlJp0ygBvBjr zTLGlzcM/PRw3r4jJqa8KhAVRsHnDa2Ht5RfBbbzuWM4uzzTD4yHTCgmpIp8sGPp AnlKbqCCfc73njcnSb80EV3ySQ9Ns3EGgwY3Q9elB+ouU63MzG9wj5p/0i9U7afQ 1TFgE6awP2sOSCLBWa3cMxPubl6lZ4G4EwTcxuOPpeahj/tsqbzhwiCKCXa8OsWz lAKqzWOpaaHFbxJXRxU5i3RWx2LPF9Z8b7Xx1nd+AwtPNaG8bJJJqgTJrMoAJW+h 4mZ/Tjox0cyRL6k32muMaQtPA458+dOP/UkRoEYEk3IeDCecekjsP1Rwal/Bd6Ex XbcRWExY7CYC+80fs7zOsDKDJjxyma87I0t+cD45DCh1uGRgBDPMS0+VK5o/nftK uPt2swGNcr+Imluf4jCRQqA/iGKrmo64h8gqeEDgD8DtZaG9RuEm1bBwBmNe0Sok YMlODDvrJjw6Ym+pHb3eMxluvJ2X4Qyrd+1Y+vq6/fkus+YNA563RMUZg+jC0pfW wsJD5qOetiP38lsfia2CtZi31jybmmYKjF/ErLxADLepS55EyaQ= =UDI2 -----END PGP SIGNATURE----- --=-=-=--