From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: "René Scharfe" <l.s.r@web.de>
Cc: Ondrej Pohorelsky <opohorel@redhat.com>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: Test breakage with zlib-ng
Date: Tue, 12 Dec 2023 22:18:34 +0000 [thread overview]
Message-ID: <ZXjcOtQ8s60X8FEQ@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <9feeb6cf-aabf-4002-917f-3f6c27547bc8@web.de>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
On 2023-12-12 at 17:04:55, René Scharfe wrote:
> --- >8 ---
> Subject: [PATCH] t6300: avoid hard-coding object sizes
>
> f4ee22b526 (ref-filter: add tests for objectsize:disk, 2018-12-24)
> hard-coded the expected object sizes. Coincidentally the size of commit
> and tag is the same with zlib at the default compression level.
>
> 1f5f8f3e85 (t6300: abstract away SHA-1-specific constants, 2020-02-22)
> encoded the sizes as a single value, which coincidentally also works
> with sha256.
>
> Different compression libraries like zlib-ng may arrive at different
> values. Get them from the file system instead of hard-coding them to
> make switching the compression library (or changing the compression
> level) easier.
This definitely seems like the right thing to do. I was a bit lazy at
the time and probably could have improved it then, but it's at least
good that we're doing it now.
--
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2023-12-12 22:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 14:16 Test breakage with zlib-ng Ondrej Pohorelsky
2023-12-12 17:04 ` René Scharfe
2023-12-12 20:01 ` Jeff King
2023-12-12 22:54 ` René Scharfe
2023-12-13 12:28 ` [PATCH 2/1] test-lib-functions: add object size functions René Scharfe
2023-12-14 20:59 ` Jeff King
2023-12-19 16:42 ` René Scharfe
2023-12-21 9:47 ` [PATCH] t1006: add tests for %(objectsize:disk) Jeff King
2023-12-21 12:19 ` René Scharfe
2023-12-21 21:30 ` Jeff King
2023-12-21 23:13 ` René Scharfe
2023-12-23 10:09 ` [PATCH v2] " Jeff King
2023-12-24 9:30 ` René Scharfe
2023-12-23 10:18 ` [PATCH] " Jeff King
2023-12-24 9:30 ` René Scharfe
2023-12-12 22:18 ` brian m. carlson [this message]
2023-12-12 22:30 ` Test breakage with zlib-ng Junio C Hamano
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=ZXjcOtQ8s60X8FEQ@tapette.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=l.s.r@web.de \
--cc=opohorel@redhat.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 NNTP newsgroup(s).