From: Tomas Volf <~@wolfsden.cz>
To: Suhail <suhail@bayesians.ca>
Cc: Simon Tournier <zimon.toutoune@gmail.com>,
Felix Lechner via <help-guix@gnu.org>,
Julien Lepiller <julien@lepiller.eu>,
Felix Lechner <felix.lechner@lease-up.com>
Subject: Re: Turning off tests leads to a different store item
Date: Fri, 3 Nov 2023 14:08:16 +0100 [thread overview]
Message-ID: <ZUTwwCt2UoqfUJ03@ws> (raw)
In-Reply-To: <87r0l818ka.fsf@>
[-- Attachment #1: Type: text/plain, Size: 662 bytes --]
On 2023-11-02 15:25:33 +0000, Suhail wrote:
> [..]
>
> The hypothetical test derivation leaves the build artifact unchanged,
> but does communicate some "side" information. It's like a fixed-output
> derivation carrying some metadata (further elaboration below).
I am not aware of any, but I wonder if there are test suites that actually
modify the built binary, for example by patching a bool flag `was_tested' to #t.
Runtime behavior could then differ based on the flag. Do you have some ideas
how to detect/deal with this?
T.
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-11-03 20:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 15:25 Turning off tests leads to a different store item Suhail
2023-11-02 17:02 ` Simon Tournier
2023-11-02 17:46 ` Simon Tournier
2023-11-03 13:08 ` Tomas Volf [this message]
2023-11-03 20:44 ` Suhail
[not found] <6543bf92.d40a0220.bbcd0.1118SMTPIN_ADDED_BROKEN@mx.google.com>
2023-11-02 16:03 ` Greg Hogan
-- strict thread matches above, loose matches on Subject: below --
2023-11-02 17:25 Suhail
2023-11-02 18:54 Suhail
2023-11-03 9:33 ` Simon Tournier
2023-11-03 14:13 Suhail
2023-11-05 12:07 ` Simon Tournier
[not found] <65429087.0c0a0220.5908c.4d60SMTPIN_ADDED_BROKEN@mx.google.com>
2023-11-07 18:58 ` Maxim Cournoyer
2023-11-07 21:58 ` Csepp
2023-11-08 2:53 ` Felix Lechner via
2023-11-08 14:45 ` Maxim Cournoyer
2023-11-08 17:07 ` Felix Lechner via
2023-11-08 18:18 ` Vagrant Cascadian
2023-11-08 19:20 ` Saku Laesvuori
2023-11-08 22:21 ` Simon Tournier
2023-11-09 3:17 ` Maxim Cournoyer
2023-11-09 7:37 ` Simon Tournier
2023-11-09 15:04 ` Maxim Cournoyer
2023-11-16 9:31 ` Simon Tournier
2023-11-18 4:38 ` Maxim Cournoyer
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=ZUTwwCt2UoqfUJ03@ws \
--to=~@wolfsden.cz \
--cc=felix.lechner@lease-up.com \
--cc=help-guix@gnu.org \
--cc=julien@lepiller.eu \
--cc=suhail@bayesians.ca \
--cc=zimon.toutoune@gmail.com \
/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.
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).