From: Ben Peart <firstname.lastname@example.org> To: "Ævar Arnfjörð Bjarmason" <email@example.com>, "Jeff King" <firstname.lastname@example.org> Cc: Stefan Beller <email@example.com>, firstname.lastname@example.org, Junio C Hamano <email@example.com>, Derrick Stolee <firstname.lastname@example.org>, Ben Peart <Ben.Peart@microsoft.com> Subject: Re: [PATCH 2/4] t5310: test delta reuse with bitmaps Date: Sat, 1 Sep 2018 18:46:40 -0400 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> On 9/1/2018 4:29 PM, Ævar Arnfjörð Bjarmason wrote: > > > B.t.w. for Ben or anyone else who knows about the fsmonitor part of > this: I've long been running the whole test suite with > `GIT_FSMONITOR_TEST=$PWD/t7519/fsmonitor-all prove ...` (also along with > GIT_TEST_SPLIT_INDEX=) after all the main tests pass as additional > stress testing. > > It's not documented under the "special setups" section. So I was going > to add it, but I see that in 5c8cdcfd80 ("fsmonitor: add test cases for > fsmonitor extension", 2017-09-22) it's documented that you should also > set GIT_FORCE_PRELOAD_TEST=true, is that needed for GIT_FSMONITOR_TEST? > Or is it yet another mode, and if so to be combined with fsmonitor in > particular, or stand-alone? > I was unaware of the "special setups" section until recently so if you would add the fsmonitor information that would be great. I added the GIT_FORCE_PRELOAD_TEST as when I went to test fsmonitor I realized there was no way to manually override the default behavior and force preload to happen. I added tests into t7519-status-fsmonitor.sh that use this capability to test fsmonitor with and without preload to ensure they play nice together as I had to add logic into the preload code to mark cache entries as clean for fsmonitor. GIT_FORCE_PRELOAD_TEST should probably be added to the "special setups" as well so that the entire test suite can be used to exercise that code path. Ultimately, GIT_FSMONITOR_TEST and GIT_FORCE_PRELOAD_TEST can be used to test their respective code paths using the test suite. The challenge is that the number of potential combinations (including split index, uncommon pack modes, etc) gets large pretty quickly. >> There may be a larger lesson about tracking code coverage, but I don't >> know that most general code coverage tools would have helped (any >> overall percentage number would be too large to move). A tool that >> looked at the diff and said "of the N lines you added/touched, this >> percent is exercised in the test suite" might have been useful. > > This would be very useful. >
next prev parent reply other threads:[~2018-09-01 22:46 UTC|newest] Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-08-21 18:41 [PATCH] test-tool.h: include git-compat-util.h Jeff King 2018-08-21 19:03 ` Junio C Hamano 2018-08-21 19:06 ` [PATCH 1/6] t/perf: factor boilerplate out of test_perf Jeff King 2018-08-21 19:06 ` [PATCH 2/6] t/perf: factor out percent calculations Jeff King 2018-08-21 19:06 ` [PATCH 3/6] t/perf: add infrastructure for measuring sizes Jeff King 2018-08-22 13:40 ` Derrick Stolee 2018-08-22 15:31 ` Jeff King 2018-08-21 19:06 ` [PATCH 4/6] t/perf: add perf tests for fetches from a bitmapped server Jeff King 2018-08-21 19:07 ` [PATCH 5/6] pack-bitmap: save "have" bitmap from walk Jeff King 2018-08-21 19:47 ` Derrick Stolee 2018-08-21 19:54 ` Jeff King 2018-08-31 15:23 ` Ævar Arnfjörð Bjarmason 2018-08-31 22:55 ` Jeff King 2018-09-01 7:41 ` [PATCH 0/4] un-breaking pack-objects with bitmaps Jeff King 2018-09-01 7:44 ` [PATCH 1/4] bitmap_has_sha1_in_uninteresting(): drop BUG check Jeff King 2018-09-01 7:48 ` [PATCH 2/4] t5310: test delta reuse with bitmaps Jeff King 2018-09-01 8:03 ` Jeff King 2018-09-01 20:29 ` Ævar Arnfjörð Bjarmason 2018-09-01 22:46 ` Ben Peart [this message] 2018-09-02 5:51 ` Jeff King 2018-09-04 19:05 ` Stefan Beller 2018-09-04 19:45 ` Junio C Hamano 2018-09-04 20:02 ` Jeff King 2018-09-01 7:49 ` [PATCH 3/4] traverse_bitmap_commit_list(): don't free result Jeff King 2018-09-01 7:50 ` [PATCH 4/4] pack-bitmap: drop "loaded" flag Jeff King 2018-09-04 19:30 ` [PATCH 0/4] un-breaking pack-objects with bitmaps Stefan Beller 2018-09-04 20:03 ` Jeff King 2018-09-08 6:43 ` Ævar Arnfjörð Bjarmason 2018-09-10 16:53 ` Junio C Hamano 2018-09-10 18:48 ` Jeff King 2018-09-10 19:23 ` Junio C Hamano 2018-08-21 19:07 ` [PATCH 6/6] pack-objects: reuse on-disk deltas for thin "have" objects Jeff King 2018-08-21 19:43 ` Junio C Hamano 2018-08-21 19:50 ` Junio C Hamano 2018-08-21 20:07 ` Jeff King 2018-08-21 20:14 ` Jeff King 2018-08-21 20:52 ` Junio C Hamano 2018-08-21 21:30 ` Jeff King 2018-08-21 20:57 ` Junio C Hamano 2018-08-21 21:32 ` Jeff King 2018-08-23 0:43 ` [PATCH 0/9] trailer-parsing false positives Jeff King 2018-08-23 0:44 ` [PATCH 1/9] trailer: use size_t for string offsets Jeff King 2018-08-23 0:45 ` [PATCH 2/9] trailer: use size_t for iterating trailer list Jeff King 2018-08-23 0:46 ` [PATCH 3/9] trailer: pass process_trailer_opts to trailer_info_get() Jeff King 2018-08-23 0:48 ` [PATCH 4/9] interpret-trailers: tighten check for "---" patch boundary Jeff King 2018-08-23 0:49 ` [PATCH 5/9] interpret-trailers: allow suppressing "---" divider Jeff King 2018-08-23 0:50 ` [PATCH 6/9] pretty, ref-filter: format %(trailers) with no_divider option Jeff King 2018-08-23 0:50 ` [PATCH 7/9] sequencer: ignore "---" divider when parsing trailers Jeff King 2018-08-23 0:50 ` [PATCH 8/9] append_signoff: use size_t for string offsets Jeff King 2018-08-23 0:51 ` [PATCH 9/9] sequencer: handle ignore_footer when parsing trailers Jeff King 2018-08-23 18:30 ` [PATCH 0/9] trailer-parsing false positives Junio C Hamano 2018-08-24 7:26 ` Jeff King 2018-08-21 20:00 ` [PATCH 6/6] pack-objects: reuse on-disk deltas for thin "have" objects Jeff King
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 \ --email@example.com \ --firstname.lastname@example.org \ --cc=Ben.Peart@microsoft.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH 2/4] t5310: test delta reuse with bitmaps' \ /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
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).