unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCHES] Add totem
Date: Wed, 24 Jun 2015 22:21:05 +0200	[thread overview]
Message-ID: <87oak4x3gu.fsf@gnu.org> (raw)
In-Reply-To: <878ub9k5ck.fsf@netris.org> (Mark H. Weaver's message of "Wed, 24 Jun 2015 02:06:35 -0400")

Mark H Weaver <mhw@netris.org> skribis:

> ludo@gnu.org (Ludovic Courtès) writes:
>
>>> From ba786fa3d1d7896336dca3b364bb630142c30fa1 Mon Sep 17 00:00:00 2001
>>> From: Mark H Weaver <mhw@netris.org>
>>> Date: Sat, 20 Jun 2015 21:09:54 -0400
>>> Subject: [PATCH 2/3] gnu: Add grilo-plugins.
>>>
>>> * gnu/packages/gnome.scm (grilo-plugins): New variable.
>>
>> [...]
>>
>>> +     `(#:make-flags (list (string-append "GRL_PLUGINS_DIR="
>>> +                                         %output
>>> +                                         "/lib/grilo-"
>>> +                                         ,(version-major+minor version)))
>>> +       ;; XXX FIXME: Investigate test failure:
>>> +       ;;   TEST: test_apple_trailers... (pid=8718)
>>> +       ;;     /apple-trailers/browse/count:
>>> +       ;;   ERROR:test_apple_trailers.c:88:test_browse_count: assertion failed: (source)
>>> +       ;;   FAIL
>>> +       #:tests? #f))
>>
>> Would it be OK to skip just this for now?  If that’s too much, we can
>> leave it for later.
>
> "make check" aborts after this failure, which is the first test.  I
> tried "make -k check" and found that _all_ tests fail with the same
> assertion failure when run in the build container.
>
> However, if I run "make -k check" on the failed build directory in
> /tmp/nix-build-* from outside of the build container, all but one of the
> tests succeeds.  This when using the precise environment variable
> settings from the build and no others.  Using strace, I found that it
> was accessing the system dbus, so I guess that's the problem.

Ah OK.  It’s really a bug in their test framework IMO.  It’s probably OK
to punt on this one and document these findings in the comment.

Thanks,
Ludo’.

      reply	other threads:[~2015-06-24 20:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-21  4:21 [PATCHES] Add totem Mark H Weaver
2015-06-22 19:24 ` Ludovic Courtès
2015-06-24  5:58   ` How to handle required plugins and dbus services for GNOME Programs? Mark H Weaver
2015-06-24 15:45     ` 宋文武
2015-06-25  4:07       ` Mark H Weaver
2015-06-25  7:42         ` 宋文武
2015-06-24 20:47     ` Ludovic Courtès
2015-06-25  5:00     ` David Hashe
2015-07-09  6:30     ` Mark H Weaver
2015-07-09 13:00       ` 宋文武
2015-07-10 21:24       ` Ludovic Courtès
2015-06-24  6:06   ` [PATCHES] Add totem Mark H Weaver
2015-06-24 20:21     ` Ludovic Courtès [this message]

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=87oak4x3gu.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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 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).