[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GNUnet-developers] Incorrect test environments

From: Christian Grothoff
Subject: Re: [GNUnet-developers] Incorrect test environments
Date: Mon, 25 Aug 2008 14:57:06 -0600
User-agent: KMail/1.9.9

On Monday 25 August 2008 01:55:08 pm Ludovic Courtès wrote:
> Hi again,
> While packaging GNUnet for NixOS, I tried running the test suite without
> much success.  Builds are done in a chroot, which helps catch errors.
> The most common problem that I've found is tests not being executed in
> the right environment: for instance, $LTDL_LIBRARY_PATH doesn't contain
> the directory where needed modules live, $PATH doesn't contain the
> `gnunetd' directory, etc.

Please read the README file with particular emphasis on the wording 
around "GNUNET_PREFIX".  This should allow you to solve part of your problem.

> In addition, core GNUnet libraries do not honor $TMPDIR (the build
> chroot doesn't have `/tmp' and expects applications to honor it; it's a
> nice thing to have anyway, and it pleases SuSv2 [0]).

We should do this, I agree.

> Patches are attached.  The test-related patches are against
> `' can be easily adapted to `.am'.  It's not a complete list
> of fixes as I eventually gave up trying to run the test-suite due to
> lack of time.
> Besides, any idea of which tests are likely to fail within a chroot?

In general I would hope none.

> Likewise, are there tests that rely on a network connection?

All of the "make check" tests were written to pass with just loopback.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]