all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: 16534@debbugs.gnu.org, Sree Harsha Totakura <sreeharsha@totakura.in>
Subject: bug#16534: gstreamer-1.0.10 tests fail
Date: Fri, 24 Jan 2014 22:35:58 +0100	[thread overview]
Message-ID: <87iot9xdtt.fsf@gnu.org> (raw)
In-Reply-To: <20140124210403.GA369@debian> (Andreas Enge's message of "Fri, 24 Jan 2014 22:04:03 +0100")

Andreas Enge <andreas@enge.fr> skribis:

> On Fri, Jan 24, 2014 at 11:25:39AM +0100, Sree Harsha Totakura wrote:
>> One testcase for gstreamer-1.0.10 fails on my computer.  The following
>> output is seen when this happens:
>
> I confirm that this happens now systematically on my machine also.

Same here (x86_64-linux).  Unfortunately, nothing relevant at
<https://bugzilla.gnome.org/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=GStreamer&content=gstbus+test_watch_with_custom_context>
AFAICS.

> According to hydra:
> Last successful build 2013-12-30
> First broken build 2014-01-19
>
> I wonder if this is related to the changes in the build daemon?
> Did the content of the chroot also change?

No.  Also, ‘guix-daemon’ on hydra.gnu.org hasn’t been updated.

The last good commit was 40fed2d according to Hydra, and then it’s not
clear when it broke because Hydra wasn’t healthy, but the GLib update is
a suspect.

Thanks,
Ludo’.

  reply	other threads:[~2014-01-24 21:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-24 10:25 bug#16534: gstreamer-1.0.10 tests fail Sree Harsha Totakura
2014-01-24 21:04 ` Andreas Enge
2014-01-24 21:35   ` Ludovic Courtès [this message]
2014-01-26 11:12     ` Andreas Enge
2014-01-26 19:32       ` Ludovic Courtès
2014-01-26 20:14       ` Ludovic Courtès
2014-04-07 21:41     ` Ludovic Courtès
2014-04-08 14:08       ` Andreas Enge
2014-04-08 14:51         ` Ludovic Courtès

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=87iot9xdtt.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=16534@debbugs.gnu.org \
    --cc=andreas@enge.fr \
    --cc=sreeharsha@totakura.in \
    /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.