From: taylanbayirli@gmail.com (Taylan Ulrich Bayırlı/Kammer)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/1] Add lz4 (C implementation)
Date: Wed, 09 Sep 2015 23:26:36 +0200 [thread overview]
Message-ID: <87vbbj5lo3.fsf@T420.taylan> (raw)
In-Reply-To: <cover.1441832565.git.leo@famulari.name> (Leo Famulari's message of "Wed, 9 Sep 2015 17:04:11 -0400")
Leo Famulari <leo@famulari.name> writes:
> This patch adds the C reference implementation of the lz4 compression
> algorithm.
>
> I'm looking for advice regarding the tests. The tests take >30 minutes
> on my on my quad-core i5 with 8 gigabytes of RAM and they require
> Valgrind as a native-input. This seems excessive to me but if users
> install binary substitutes, they won't run the tests or need to
> install Valgrind, right? And if distributions won't test software,
> then who will?
Indeed users won't have to go through that unless they build from
source, and Valgrind won't become a run-time dependency so long as the
produced package does not contain any references to any files from the
Valgrind package.
Guix contains a lot of software with build and test phases that take a
very long time. When I was working on Qt it would take 5 GB of disk
space and 6 hours to build every time. Though that was a pathological
case and this program is tiny in comparison, I'd still say ~30 minutes
is harmless. It's annoying, but that's the price of disciplined work.
Taylan
next prev parent reply other threads:[~2015-09-09 21:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 21:04 [PATCH 0/1] Add lz4 (C implementation) Leo Famulari
2015-09-09 21:04 ` [PATCH 1/1] gnu: Add lz4 Leo Famulari
2015-09-09 21:26 ` Taylan Ulrich Bayırlı/Kammer [this message]
2015-09-09 22:16 ` [PATCH 0/1] Add lz4 (C implementation) Leo Famulari
2015-09-13 10:10 ` 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=87vbbj5lo3.fsf@T420.taylan \
--to=taylanbayirli@gmail.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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.