From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: gst-plugins-base: Test suite failed: FAIL: elements/opus
Date: Tue, 19 Jun 2018 16:13:09 +0200 [thread overview]
Message-ID: <8736xig8zu.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <877emvj5uv.fsf@gmail.com> (Pierre Neidhardt's message of "Tue, 19 Jun 2018 14:52:40 +0200")
Hello,
Pierre Neidhardt <ambrevar@gmail.com> writes:
> I can't update my packages `guix package -u`, gst-plugins-base fails:
[...]
> FAIL: elements/opus
> ===================
>
> Running suite(s): opus
> 33%: Checks: 6, Failures: 0, Errors: 4
> gstcheck.c:596:E:general:test_opus_encode_nothing:0: (after this point) Received signal 11 (Segmentation fault)
> gstcheck.c:596:E:general:test_opus_encode_samples:0: (after this point) Received signal 11 (Segmentation fault)
> gstcheck.c:596:E:general:test_opus_encode_properties:0: (after this point) Received signal 11 (Segmentation fault)
> elements/opus.c:429:E:general:test_opus_decode_plc_timestamps_with_fec:0: (after this point) Received signal 11 (Segmentation fault)
> Check suite opus ran in 0.014s (tests failed: 4)
> FAIL elements/opus (exit status: 4)
[...]
> Anyone else?
Ditto. It breaks wine upgrade (even wine64).
Quick and dirty fix: what about disabling elements/opus test? It doesn't
look like a vital part.
Regards,
--
Nicolas Goaziou 0x80A93738
next prev parent reply other threads:[~2018-06-19 14:13 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8736xig8zu.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=ambrevar@gmail.com \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.