unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Giovanni Biscuolo <g@xelera.eu>
To: Marius Bakke <mbakke@fastmail.com>
Cc: Platoxia <platoxia@protonmail.com>, 35521@debbugs.gnu.org
Subject: bug#35521: Mariadb test suite failures on x86_64-linux
Date: Fri, 12 Jul 2019 10:24:04 +0200	[thread overview]
Message-ID: <878st3u0d7.fsf@roquette.mug.biscuolo.net> (raw)
In-Reply-To: <87ims8mds7.fsf@devup.no>

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

Hi Marius,

Marius Bakke <mbakke@fastmail.com> writes:

[...]

> Looking further into the changes between 10.1.37 and 10.1.38, I notice
> the 'tokudb.*' tests were enabled:
>
> https://github.com/MariaDB/server/commit/4c490d6df63695dc97b2c808e59954e6877d3a51

The very first thing I noticed lookng at that commit is it's subject:
"Updated list of unstable tests for 10.1.38 release"

The first comments of that file states:

--8<---------------cut here---------------start------------->8---
#  List the test cases which, unlike tests from disabled.def files,
#  can still be run on the current tree meaningfully, but are known
#  or suspected to fail sporadically on different reasons.
#
#  Most common reasons are either test failures observed in buildbot,
#  or recent modifications to the tests which make their stability
#  unknown.
#
#  Tests included due to recent modifications are later removed from the
#  list, if during a certain period they do not fail (and are not
#  modified again). Tests included due to intermittent failures are
#  removed when corresponding bug reports are closed.
#
#  Separate the test case name and the comment with ':'.
#
#    <suitename>.<testcasename> : MDEV-xxxxx - <comment>
#
#  '*' wildcard in testcase names is supported.
#
#  To use the list, run MTR with --skip-test-list=unstable-tests option.
--8<---------------cut here---------------end--------------->8---

So *all* those rests _are_ considered unstable upstream.

IMHO they should be *selectively* skipped when they causes build
problems in Guix, including non-deterministic frequent ones like in this
case.

> Watching the build on Berlin in real time, I also see that the test
> output grind nearly to a halt while running those.
> 'tokudb.hotindex-insert-2' took 2700439 milliseconds, or 45 minutes, if
> I'm reading the test output correctly.

The same is happening upstream:
https://jira.mariadb.org/browse/MDEV-15198
https://jira.mariadb.org/browse/MDEV-16040 (duplicate of the above)
https://jira.mariadb.org/browse/MDEV-15271

That bugs (and all others related to unstable tests) are currently
unresolved.

HTH! Gio'

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2019-07-12  8:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-01  9:18 bug#35521: Mariadb test suite failures on x86_64-linux Mark H Weaver
2019-05-01  9:47 ` Mark H Weaver
2019-07-10  6:18   ` Chris Marusich
2019-07-10 17:30     ` Marius Bakke
2019-07-10 21:32       ` Mark H Weaver
2019-07-11 20:18         ` Ludovic Courtès
2019-07-12  8:02           ` Giovanni Biscuolo
2019-07-11 22:01         ` Marius Bakke
2019-07-12  8:24           ` Giovanni Biscuolo [this message]
2019-07-12 14:58           ` Marius Bakke
2019-07-13 17:29             ` Mark H Weaver
2019-07-13 22:42               ` Marius Bakke
2019-07-14  2:35                 ` Mark H Weaver
2019-07-14 11:10                   ` Arne Babenhauserheide
2019-07-14 15:58                     ` Gábor Boskovits
2019-07-14  4:42                 ` Mark H Weaver
2019-07-14 17:17                   ` Marius Bakke
2019-07-14 18:34                     ` Mark H Weaver
2019-07-14 21:15                       ` Marius Bakke
2019-07-13 18:38             ` Mark H Weaver
2019-05-10  1:33 ` bug#35521: /gnu/store/c46sn2yfllcfi86p8227wvvr1bxssgxj-mariadb-10.1.38.drv - Failing test(s): tokudb_alter_table.hcad_all_add Platoxia

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=878st3u0d7.fsf@roquette.mug.biscuolo.net \
    --to=g@xelera.eu \
    --cc=35521@debbugs.gnu.org \
    --cc=mbakke@fastmail.com \
    --cc=platoxia@protonmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).