unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Matthew Brooks <matthewfbrooks@mailbox.org>
To: help-guix@gnu.org
Subject: Re: mariadb build fails "Failing test(s): main.mysqldump"
Date: Sun, 13 Jan 2019 22:26:19 -0600	[thread overview]
Message-ID: <20190113222619.1e5e638d@mailbox.org> (raw)
In-Reply-To: <20190108211026.78843e1c@mailbox.org>

[-- Attachment #1: Type: text/plain, Size: 915 bytes --]

Minor update, mariadb is also failing to build on my desktop now. So it looks like when it managed to complete a few weeks ago was lucky timing and not some configuration difference between my laptop and desktop.
I've also attached the log from my desktop, which is much the same as the ones from my laptop. The only failed test was "main.mysqldump", which failed in a lot of ways, but I am not familiar enough with the program or tests to make heads or tails of the errors or have any idea how to fix.

I also checked "guix gc --referrers" on mariadb, and it looks like qtbase is pulling it in.
Sadly, even after installing portgresql and mysql, guix kept trying to build mariadb, so it looks like qtbase is specifically pulling in mariadb and not just a generic database engine, so I still can't install stuff like SDL, ffmpeg, calibre, and miscellaneous other stuff, until mariadb decides to build successfully.

[-- Attachment #2: d7i5258vi0rd9ydbpr9c1vb3sxcz6h-mariadb-10.1.37.drv.bz2 --]
[-- Type: application/x-bzip, Size: 350043 bytes --]

  reply	other threads:[~2019-01-14  4:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-07  2:43 mariadb build fails "Failing test(s): main.mysqldump" Matthew Brooks
2019-01-08  5:00 ` Matthew Brooks
2019-01-09  3:12   ` Matthew Brooks
2019-01-14  4:26     ` Matthew Brooks [this message]
2019-01-23  2:06       ` Matthew Brooks
2019-01-24  2:19         ` Matthew Brooks
  -- strict thread matches above, loose matches on Subject: below --
2019-02-07  8:13 Nikolai Merinov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190113222619.1e5e638d@mailbox.org \
    --to=matthewfbrooks@mailbox.org \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).