git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] pack-bitmap: remove trace2 region from hot path

From
Taylor Blau <me@ttaylorr.com>
Date
Sep 23, 2022, 19:17 UTC
Message-ID
<Yy4GVT8VZ4dOyGDy@nand.local>
In-Reply-To
<xmqq7d1uuh5f.fsf@gitster.g>
On Fri, Sep 23, 2022 at 10:36:44AM -0700, Junio C Hamano wrote:
Show 13 quoted lines
> diff --git c/t/t5310-pack-bitmaps.sh w/t/t5310-pack-bitmaps.sh
> index 7e50f8e765..2b1efc923b 100755
> --- c/t/t5310-pack-bitmaps.sh
> +++ w/t/t5310-pack-bitmaps.sh
> @@ -455,7 +455,7 @@ test_expect_success 'verify writing bitmap lookup table when enabled' '
>  	grep "\"label\":\"writing_lookup_table\"" trace2
>  '
>
> -test_expect_success 'lookup table is actually used to traverse objects' '
> +: test_expect_success 'lookup table is actually used to traverse objects' '
>  	git repack -adb &&
>  	GIT_TRACE2_EVENT="$(pwd)/trace3" \
>  		git rev-list --use-bitmap-index --count --all &&

Yeah, I would advocate for dropping this test entirely. That trace2 marker is the only indication that is so obvious that we're using the lookup table to read bitmaps.

Perhaps the pack-bitmap helper could be taught to dump which extensions it sees, and then write a test based on that? Although that isn't really testing anything new, either, since we sometimes *notice* the extension but don't actually read anything based on it (e.g., when disabled).

So I'd be content just dropping this.

Thanks, Taylor

Previous: Derrick StoleeNext: Derrick Stolee via GitGitGadget
Message 6 of 10 in “pack-bitmap: remove trace2 region from hot path”
  1. pack-bitmap: remove trace2 region from hot pathDerrick Stolee via GitGitGadget, Sep 23, 2022
  2. Junio C HamanoSep 23, 2022
  3. Junio C HamanoSep 23, 2022
  4. Junio C HamanoSep 23, 2022
  5. Derrick StoleeSep 23, 2022
  6. Taylor BlauSep 23, 2022
  7. pack-bitmap: remove trace2 region from hot pathDerrick Stolee via GitGitGadget, Sep 26, 2022
  8. Ævar Arnfjörð BjarmasonSep 26, 2022
  9. Derrick StoleeSep 26, 2022
  10. Jeff HostetlerSep 27, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.