unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org, John J Foerch <jjfoerch@earthlink.net>
Subject: Re: [PATCH] gnu: Add di.
Date: Mon, 4 Jul 2016 15:04:46 -0400	[thread overview]
Message-ID: <20160704190446.GB8480@jasmine> (raw)
In-Reply-To: <87eg79kims.fsf@gmail.com>

On Mon, Jul 04, 2016 at 09:43:55AM +0300, Alex Kost wrote:
> John J Foerch (2016-07-04 06:47 +0300) wrote:
> > A test relating to an included perl module Filesys::di fails.  I hadn't
> > intended to include that module in the package, as all I'm interested in
> > is the 'di' binary.  Given that, I would suggest that we bypass the
> > tests.
> 
> As for me, I would also disable the tests.  All these handmade Makefiles
> in all sub-directories are a nightmare.  I think trying to figure out
> what is needed to run the tests doesn't worth it.

I agree that hand-carved Makefiles are difficult to work with.

The failing Perl-related test runs successfully if Perl is added to the
environment. However, there is another failure later on:

make[1]: Leaving directory '/tmp/guix-build-di-4.42.drv-0/di-4.42/C'
make -e tests.done
make[1]: Entering directory '/tmp/guix-build-di-4.42.drv-0/di-4.42'
## running tests
CC=gcc DC="skip"  \
	./mkconfig/runtests.sh ./tests.d
mkconfig version 1.27
## locating valid shells
   /gnu/store/b1yqjimbdh5bf9jnizd4h7yf110744j2-bash-4.3.42/bin/bash [bash4 4.3.42(1)-release] (ok)
   /gnu/store/b1yqjimbdh5bf9jnizd4h7yf110744j2-bash-4.3.42/bin/sh [sh-bash4 4.3.42(1)-release] (ok)
buildsh ... build w/mkconfig.sh ... bash4 C* sh-bash4 C* ... failed
## stopping tests due to failures in ./tests.d/ pass 1
1 tests 1 failures
Makefile:116: recipe for target 'tests.done' failed
make[1]: *** [tests.done] Error 1
make[1]: Leaving directory '/tmp/guix-build-di-4.42.drv-0/di-4.42'
Makefile:112: recipe for target 'test' failed
make: *** [test] Error 2
phase `check' failed after 64.5 seconds

I skimmed 'mkconfig/runtests.sh', but I don't understand it well enough
to debug it.

If the source code is still maintained, I bet the authors will be
willing to help. They express interest in testing and portability on the
web page.

But if everyone else prefers to skip the tests, I won't object :)

  parent reply	other threads:[~2016-07-04 19:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-02 19:13 [PATCH] gnu: Add di John J Foerch
2016-07-03 21:02 ` Leo Famulari
2016-07-03 22:03   ` John J Foerch
2016-07-04  3:47     ` John J Foerch
2016-07-04  6:43       ` Alex Kost
2016-07-04 15:18         ` John J Foerch
2016-07-04 19:07           ` Leo Famulari
2016-07-05  1:53             ` John J Foerch
2016-07-07 16:30               ` John J Foerch
2016-07-07 17:37                 ` Leo Famulari
2016-07-08  7:27                   ` Alex Kost
2016-07-08  0:40                 ` Leo Famulari
2016-07-08 14:06                   ` John J Foerch
2016-07-04 19:04         ` Leo Famulari [this message]
2016-07-05  1:56           ` John J Foerch

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=20160704190446.GB8480@jasmine \
    --to=leo@famulari.name \
    --cc=alezost@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=jjfoerch@earthlink.net \
    /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).