From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: bug#37605: [core-updates] MariaDB fails tests on armhf-linux Date: Tue, 08 Oct 2019 11:00:24 +0200 Message-ID: <87o8yr628n.fsf@devup.no> References: <8736g996l2.fsf@devup.no> <87r23r73q5.fsf@devup.no> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:60641) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iHlMj-0003cu-4V for bug-guix@gnu.org; Tue, 08 Oct 2019 05:01:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iHlMd-0005Fm-Up for bug-guix@gnu.org; Tue, 08 Oct 2019 05:01:09 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:40687) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iHlMd-0005FI-NR for bug-guix@gnu.org; Tue, 08 Oct 2019 05:01:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iHlMd-00023c-L9 for bug-guix@gnu.org; Tue, 08 Oct 2019 05:01:03 -0400 Sender: "Debbugs-submit" Resent-To: bug-guix@gnu.org Resent-Message-ID: In-Reply-To: <87r23r73q5.fsf@devup.no> 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: 37605-done@debbugs.gnu.org --==-=-= Content-Type: multipart/mixed; boundary="=-=-=" --=-=-= Content-Type: text/plain Marius Bakke writes: > Marius Bakke writes: > >> "mariadb" consistently fails a single test on the core-updates branch on >> armhf-linux: >> >> https://ci.guix.gnu.org/build/1689172/details >> >> [...] >> >> This does not happen on current 'master', so the problem was introduced >> somewhere in between ccbc1c5eb..cbc8c658d. > > Upstream bug report here: > > https://jira.mariadb.org/browse/MDEV-20573 > > I'm not sure what to do about it. We could skip it, but then users who > rely on encrypted binary logs could potentially get in trouble. I > haven't found a compile-time flag to disable just this one feature. I was able to work around it by going back to GCC 5: --=-=-= Content-Type: text/x-patch Content-Disposition: inline modified gnu/packages/databases.scm @@ -72,6 +72,7 @@ #:use-module (gnu packages dbm) #:use-module (gnu packages emacs) #:use-module (gnu packages flex) + #:use-module (gnu packages gcc) #:use-module (gnu packages gettext) #:use-module (gnu packages glib) #:use-module (gnu packages gnupg) @@ -779,6 +780,10 @@ Language.") #t)))))) (native-inputs `(("bison" ,bison) + ;; XXX: On armhf, use GCC 5 to work around . + ,@(if (string-prefix? "armhf" (%current-system)) + `(("gcc", gcc-5)) + '()) ("perl" ,perl))) (inputs `(("jemalloc" ,jemalloc) --=-=-= Content-Type: text/plain GCC 9 did not make a difference. Workaround pushed in 2fa55c72476c73211cbb2d6b29c05a1ad58a6cf9. Let's revisit this after upgrading to MariaDB 10.4. --=-=-=-- --==-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl2cUCgACgkQoqBt8qM6 VPqJlggAvMJXG7uET0basigaoRMt2tPShVudi2VQ9nUU9BE0fKgW9eeYJQIiDdTR QWkplefShCJts764EOuckC8Aw97Yt9QaZrx8QF9vtrEKLRmF9BJnJmN1yGq1I5/P A44kw0FZjz1ApZj/dyuBKKf4Nfox5Hy4xC58E9aO7uRzkYBDTYD5i1RABZvyxnUQ IuVXL8dQoZrprsBq6YxeuAt0p99azPxjqbPPhe0dtdk/9LY1ktQE9UZM2TB3723K i7+S9hibCJrt7sT9EnXagnRPt6xwD1ni+MhNbUbDVMOosn0lSQJz59DWgMZxFWnH Rja7VhaEBbt02UdF/BXjWknWWOvJEQ== =7SNb -----END PGP SIGNATURE----- --==-=-=--