From: Ricardo Wurmus <rekado@elephly.net>
To: Leo Famulari <leo@famulari.name>
Cc: help-guix <help-guix@gnu.org>, Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: gst-plugins-base: Test suite failed: FAIL: elements/opus
Date: Wed, 20 Jun 2018 22:48:38 +0200 [thread overview]
Message-ID: <87d0wltc9l.fsf@elephly.net> (raw)
In-Reply-To: <20180620163618.GA1100@jasmine.lan>
Leo Famulari <leo@famulari.name> writes:
> On Wed, Jun 20, 2018 at 06:15:19PM +0200, Pierre Neidhardt wrote:
>> I'm till seeing this problem.
>>
>> > guix --version
>> guix (GNU Guix) d39c9efa11168f5a441ac60b3ed486f2ac0b4c73
>>
>> > guix pull -l
>> # ...
>> Generation 2 Jun 19 2018 14:10:01 (current)
>> guix d39c9ef
>> repository URL: https://git.savannah.gnu.org/git/guix.git
>> branch: origin/master
>> commit: d39c9efa11168f5a441ac60b3ed486f2ac0b4c73
>>
>>
>> I'm on a x86_64 machine with kernel 4.14.33.
>
> Okay, are you able to send a patch to disable the test and report this
> issue upstream?
On i686 the test fails with a segfault. I would be uncomfortable with
disabling the test before we understand the cause of the segfault. It
may be better to remove libopus complete if it turns out that one could
trigger the segfault at runtime, outside of the test context.
--
Ricardo
next prev parent reply other threads:[~2018-06-20 20:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 12:52 gst-plugins-base: Test suite failed: FAIL: elements/opus Pierre Neidhardt
2018-06-19 14:13 ` Nicolas Goaziou
2018-06-20 16:11 ` Leo Famulari
2018-06-20 16:15 ` Pierre Neidhardt
2018-06-20 16:36 ` Leo Famulari
2018-06-20 16:40 ` Pierre Neidhardt
2018-06-20 20:48 ` Ricardo Wurmus [this message]
2018-06-20 21:08 ` Marius Bakke
2018-06-25 19:10 ` Leo Famulari
2018-07-20 18:44 ` Leo Famulari
2018-07-20 21:22 ` Björn Höfling
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=87d0wltc9l.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
--cc=mail@nicolasgoaziou.fr \
/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).