bug#32511: mariadb 10.1.35 fails to build on x86_64

bug#32511: mariadb 10.1.35 fails to build on x86_64

[Ludovic Courtès]

Hello,

On berlin, mariadb 10.1.35 has one test failure (this is
/gnu/store/a5jm2hyalyblgjnxx5x3ly4fwvfivq5m-mariadb-10.1.35.drv, as
found in Guix commit b0cb92b2d43a2c4d5fa9b3f8c04c5732c60061e7, for
instance):

--8<---------------cut here---------------start------------->8---
The servers were restarted 933 times
Spent 43877.794 of 6960 seconds executing testcases

Failure: Failed 1/1941 tests, 99.95% were successful.

Failing test(s): tokudb_bugs.5733_innodb

The log files in var/log may give you some hint of what went wrong.

If you want to report this error, please read first the documentation
at http://dev.mysql.com/doc/mysql/en/mysql-test-suite.html

600 tests were skipped, 173 by the test itself.

mysql-test-run: *** ERROR: there were failing test cases
Backtrace:
           6 (primitive-load "/gnu/store/a0zx56s23cay93c3z4qx958m7n8?")
In ice-9/eval.scm:
   191:35  5 (_ _)
In srfi/srfi-1.scm:
    640:9  4 (for-each #<procedure 6bf900 at /gnu/store/qzsljkcllc0?> ?)
In /gnu/store/qzsljkcllc01dmdq9z0yrqri3ajam3vp-module-import/guix/build/gnu-build-system.scm:
   799:31  3 (_ _)
In ice-9/eval.scm:
    619:8  2 (_ #(#(#<directory (guile-user) 7cb140>) #t))
In ice-9/boot-9.scm:
    142:2  1 (dynamic-wind #<procedure 9a28e0 at ice-9/eval.scm:330?> ?)
In /gnu/store/qzsljkcllc01dmdq9z0yrqri3ajam3vp-module-import/guix/build/utils.scm:
    616:6  0 (invoke _ . _)

/gnu/store/qzsljkcllc01dmdq9z0yrqri3ajam3vp-module-import/guix/build/utils.scm:616:6: In procedure invoke:
Throw to key `srfi-34' with args `(#<condition &invoke-error [program: "./mtr" arguments: ("--verbose" "--retry=3" "--testcase-timeout=40" "--suite-timeout=600" "--parallel" "8" "--skip-test-list=unstable-tests") exit-status: 1 term-signal: #f stop-signal: #f] 9e1680>)'.
builder for `/gnu/store/a5jm2hyalyblgjnxx5x3ly4fwvfivq5m-mariadb-10.1.35.drv' failed with exit code 1
--8<---------------cut here---------------end--------------->8---

Complete log is at
<https://berlin.guixsd.org/log/37ldf3jfbq8qv0i0bpfrbbjd4ska605l-mariadb-10.1.35>.

Note that this failure, in turn, prevents qtbase and icecat from being
built, so we should probably find a quick stop-gap if that turns out to
be tricky.

Ideas?

Ludo’.

bug#32511: mariadb 10.1.35 fails to build on x86_64

[Mark H Weaver]

ludo@gnu.org (Ludovic Courtès) writes:

> On berlin, mariadb 10.1.35 has one test failure (this is
> /gnu/store/a5jm2hyalyblgjnxx5x3ly4fwvfivq5m-mariadb-10.1.35.drv, as
> found in Guix commit b0cb92b2d43a2c4d5fa9b3f8c04c5732c60061e7, for
> instance):

FWIW, after staging was merged, I also ran into a problem building
mariadb on my x86_64 GuixSD system, where I build everything locally.
It failed several times in a row, always with just 1 test failure.  The
problem turned out to be that I didn't have enough free disk space.
Buried in the mountains of output, which I found quite difficult to
navigate (searching for "[ fail ]" helped), I eventually found a message
about unsufficient space.  5 GB of free space wasn't enough, but ~12 GB
was.

      Mark

bug#32511: mariadb 10.1.35 fails to build on x86_64

[Ludovic Courtès]

Hi Mark,

Mark H Weaver <mhw@netris.org> skribis:

> ludo@gnu.org (Ludovic Courtès) writes:
>
>> On berlin, mariadb 10.1.35 has one test failure (this is
>> /gnu/store/a5jm2hyalyblgjnxx5x3ly4fwvfivq5m-mariadb-10.1.35.drv, as
>> found in Guix commit b0cb92b2d43a2c4d5fa9b3f8c04c5732c60061e7, for
>> instance):
>
> FWIW, after staging was merged, I also ran into a problem building
> mariadb on my x86_64 GuixSD system, where I build everything locally.
> It failed several times in a row, always with just 1 test failure.  The
> problem turned out to be that I didn't have enough free disk space.
> Buried in the mountains of output, which I found quite difficult to
> navigate (searching for "[ fail ]" helped), I eventually found a message
> about unsufficient space.  5 GB of free space wasn't enough, but ~12 GB
> was.

Indeed, I’ve built it on berlin itself with --no-build-hook (that way, I
was sure there was enough space available), and it passed.

The lesson here is that we might not be GC’ing enough on the build
machines behind berlin.  Any idea, Ricardo?

Also, I wonder if we should report it upstream so that they arrange to
skip the test when insufficient space is available.  Unfortunately we
don’t have many clues in the build log to provide them.  :-/

Thoughts?

Ludo’.

bug#32511: mariadb 10.1.35 fails to build on x86_64

[Sarah Morgensen]

Hello,

ludo@gnu.org (Ludovic Courtès) writes:

> Hello,
>
> On berlin, mariadb 10.1.35 has one test failure (this is
> /gnu/store/a5jm2hyalyblgjnxx5x3ly4fwvfivq5m-mariadb-10.1.35.drv, as
> found in Guix commit b0cb92b2d43a2c4d5fa9b3f8c04c5732c60061e7, for
> instance):
>
> The servers were restarted 933 times
> Spent 43877.794 of 6960 seconds executing testcases
>
> Failure: Failed 1/1941 tests, 99.95% were successful.
>
> Failing test(s): tokudb_bugs.5733_innodb

Closing this old bug; this was "fixed" in bba7a77 by disabling the
TokuDB backend; for more info:
https://issues.guix.gnu.org/35521

--
Sarah