GNU bug report logs - #36464
gstreamer test timing out

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Steffen Rytter Postas <nc <at> scalehost.eu>
Subject: bug#36464: closed (Re: bug#36464: gstreamer test timing out)
Date: Thu, 21 May 2020 20:27:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#36464: gstreamer test timing out

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 36464 <at> debbugs.gnu.org.

-- 
36464: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=36464
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Marius Bakke <mbakke <at> fastmail.com>
To: Steffen Rytter Postas <nc <at> scalehost.eu>, 36464-done <at> debbugs.gnu.org
Subject: Re: bug#36464: gstreamer test timing out
Date: Thu, 21 May 2020 22:26:42 +0200

[Message part 3 (text/plain, inline)]

Steffen Rytter Postas <nc <at> scalehost.eu> writes:

> Upon finishing the build, the gstreamer package is tested, and it has a
> single failure, which is the following:
>
> gst/gstelement.c:844:E:element tests:test_foreach_pad:0: (after this
> point) Test timeout expired
> Check suite gst_element ran in 30.164s (tests failed: 1)
> FAIL gst/gstelement (exit status: 1)

I believe this is fixed with commit
f510b56a15e05b53cc19f3a4131232a6bf81eb2e, currently residing on the
'staging' branch.

Thanks for the report, and sorry for the delay!

[signature.asc (application/pgp-signature, inline)]

[Message part 5 (message/rfc822, inline)]

From: Steffen Rytter Postas <nc <at> scalehost.eu>
To: bug-guix <at> gnu.org
Subject: gstreamer test timing out
Date: Mon, 1 Jul 2019 22:55:16 +0200

Hi,

I've been having a few issues with the Jupyter package. First and
foremost, this is my first time trying it out with Guix. Previously I
have had it running using Docker, but I prefer the modularity and
programmability of Guix, not to mention the rest of the amazing concepts
it brings.

However, nothing is perfect, and as we'll see here, that is indeed true.
Let it ne known that I've tested this on my desktop, my work laptop, and
my netbook, and only my netbook exhibits any issues.

Both environments use the same command to execute, and are using `guix
environment` to start the Jupyter notebook system:

`LC_ALL=C guix environment -C -N --pure -m env.scm -- jupyter-notebook`

The `env.scm` file used, is as follows:


(define-packages '(
    "glibc-utf8-locales"
    "coreutils-minimal"
    "bash"
    "python"
    "jupyter"
    ))
(use-modules (gnu packages))
(packages->manifest (map specification->package packages))

When attempting the above, the package "gstreamer" is attempted built
(which is fine, when no substitutes are available, this is the intended
behaviour of course), and takes quite a while (this is a dual core
800Mhz netbook from 2012. Not very impressive).

Upon finishing the build, the gstreamer package is tested, and it has a
single failure, which is the following:

gst/gstelement.c:844:E:element tests:test_foreach_pad:0: (after this
point) Test timeout expired
Check suite gst_element ran in 30.164s (tests failed: 1)
FAIL gst/gstelement (exit status: 1)

As this appears to be a timeout, I am unable to reproduce this on my
faster systems.

Sincerely,

Steffen Rytter Postas

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.