From: "Ludovic Courtès" <ludo@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: Platoxia <platoxia@protonmail.com>, 35521@debbugs.gnu.org
Subject: bug#35521: Mariadb test suite failures on x86_64-linux
Date: Thu, 11 Jul 2019 22:18:44 +0200 [thread overview]
Message-ID: <87ftncqq8r.fsf@gnu.org> (raw)
In-Reply-To: <87ef2xlgmb.fsf@netris.org> (Mark H. Weaver's message of "Wed, 10 Jul 2019 17:32:49 -0400")
Hi Mark,
Mark H Weaver <mhw@netris.org> skribis:
> Marius Bakke <mbakke@fastmail.com> writes:
>
>> Chris Marusich <cmmarusich@gmail.com> writes:
>>
>>> Hi,
>>>
>>> I've been encountering this failure off and on for a few weeks now, and
>>> I'd like to help fix it. In short, it seems like non-deterministic test
>>> failures, to me. I think we should gather data and report the issue
>>> upstream, and maybe disable the offending tests in the meantime.
>>
>> I agree. I notice many of these failing tests are for the TokuDB
>> backend, which I doubt anyone is using in Guix anyway.
>>
>> Here is a patch that disables all tests mentioned in this report. I
>> would like to push it to core-updates. Are there others?
>
> I'm concerned by how frequently and casually we simply disable failing
> tests. What is the utility of running test suites at all, if this is
> how we respond?
I don’t think anyone is happy with that. The alternative seems to be:
keeping an older version that perhaps didn’t have these problems but may
have known bugs and security issues, or keeping a package that fails to
build for a possibly long time.
I think disabling specific tests is the least bad of these options. In
this case, we know that the offending tests relate to a specific
backend, and one can at least assume that potential issues are in that
area. So I do think that this is an appropriate response.
Of course, in any such case, we should report the issue upstream, even
if we all too well know that non-deterministic test failures are hard to
address…
Ludo’.
next prev parent reply other threads:[~2019-07-11 20:20 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 [this message]
2019-07-12 8:02 ` Giovanni Biscuolo
2019-07-11 22:01 ` Marius Bakke
2019-07-12 8:24 ` Giovanni Biscuolo
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=87ftncqq8r.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=35521@debbugs.gnu.org \
--cc=mhw@netris.org \
--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).