From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53859) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1edtbo-0005QO-07 for guix-patches@gnu.org; Tue, 23 Jan 2018 03:07:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1edtbi-000887-Fp for guix-patches@gnu.org; Tue, 23 Jan 2018 03:07:08 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:59298) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1edtbi-00087z-B1 for guix-patches@gnu.org; Tue, 23 Jan 2018 03:07:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1edtbi-0003aM-48 for guix-patches@gnu.org; Tue, 23 Jan 2018 03:07:02 -0500 Subject: [bug#30030] [PATCH core-updates] gnu: java-jeromq: Update to 0.4.3. Resent-Message-ID: From: Chris Marusich References: <20180108201529.11328-1-boskovits@gmail.com> Date: Tue, 23 Jan 2018 00:06:04 -0800 In-Reply-To: <20180108201529.11328-1-boskovits@gmail.com> ("=?UTF-8?Q?G=C3=A1bor?= Boskovits"'s message of "Mon, 8 Jan 2018 21:15:29 +0100") Message-ID: <87lggp579v.fsf@garuda.local.i-did-not-set--mail-host-address--so-tickle-me> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: =?UTF-8?Q?G=C3=A1bor?= Boskovits Cc: 30030@debbugs.gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable G=C3=A1bor Boskovits writes: > * gnu/packages/java.scm (java-jeromq): Update to 0.4.3. Unfortunately, when this patch is applied to commit f3cd6633ce7348fb92735d6cd708bdc8b3b063ee (the current tip of core-updates), the "check" phase of the build fails. Actually, it fails even before the patch, so you this change doesn't break it. The failures are not deterministic. Various classes fail, and it's not always the same one every time. I briefly looked at the failures, and I couldn't make much sense of it. I think there are two avenues of investigation: 1) Git bisect to find out which commit introduced the break. 2) Report the failure(s) upstream. =2D-=20 Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAlpm7OwACgkQ3UCaFdgi Rp0frA/8DPQrj95fvHLvPEQ3zUdzviw2Vn4wwV5eZG8sSPboKf5JEIMcELFGTbdx BknUTtL11RpkCgOdMw7eLEiYJLJBfR8cBM/qGHDQJ6Qzo7+tYOo9ZkHBp8NQJXDb LTor3yhWQNjQtp2+cvPsEevzIg2B4Nx24jO5br3jU41TWuHnA/0wJBDvWQFbNq4H mZtRs3MYDguPksGcDMp4OpftOw8BLKPRErwe2j3ZDTBO+JIFD0SA8ScEZMvPOm/h 9NWFgyzc5or+7hz+vj/Bx0vsM6lhpJGobm54tjM0fFNIWw7QiCr0wBfB8RUp0/m8 RiPRRTbIFbqKgqynSc2AJstp8IlG8xeJJV6JJYsQ7lwbV1P2XmQ6KuNT5YK5Eus/ iyXZDppgmaNrWixHZSWnzOIwQj+U6Z6cj/9j8km6hN+dAoPUx5qvRa+ZbKtc/t5+ gWFAaBtWlie6zk8bCyWm1hTeE66SRvtxpqv/D59lrJ2s9WkdpjOHuPkqY/vRvhG1 za1vHExxV4DuhEEwqUkFn0Zq5i/js49Mj9ZdBRdU7tO8hAUiuTHRunvoie5Du22B GXVFBfIFI7g7qy57F4m3CPcEs6mv3mqZhYZfdKXzNaNUoeVlysG0F3xBqE8q3+kh bOIVzOcM2AAgVpnZ8Nh2UYL0HDG7iu69N9X1RQ82c1r8ZHH3ZSo= =ZmyE -----END PGP SIGNATURE----- --=-=-=--