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

Re: [PATCH 2/8] tests: always test fetch of unreachable with v0

From
Jeff King <peff@peff.net>
Date
Feb 21, 2019, 13:49 UTC
Message-ID
<20190221134954.GC21406@sigill.intra.peff.net>
In-Reply-To
<20190214195825.125751-1-jonathantanmy@google.com>
On Thu, Feb 14, 2019 at 11:58:25AM -0800, Jonathan Tan wrote:
Show 14 quoted lines
> > On Tue, Feb 05, 2019 at 04:21:16PM -0800, Jonathan Tan wrote:
> > 
> > > Some tests check that fetching an unreachable object fails, but protocol
> > > v2 allows such fetches. Unset GIT_TEST_PROTOCOL_VERSION so that these
> > > tests are always run using protocol v0.
> > 
> > I think this is reasonable, but just musing on a few things:
> > 
> >   1. Are we sure going forward that we want to retain this behavior? I
> >      feel like we discussed this on the list recently with no real
> >      conclusion, but I'm having trouble digging it up in the archive.
> 
> One such discussion is here:
> https://public-inbox.org/git/20181214101232.GC13465@sigill.intra.peff.net/

Thanks, that was what I was thinking of, though there doesn't seem to have been much discussion in response. :)

Show 12 quoted lines
> >   2. If it does change, is there any way we could automatically find
> >      spots like this that would then need to be undone? I cannot think
> >      of a good solution, and I don't think it's a show-stopper not to
> >      have one, but I thought I'd put it forward as a concept.
> 
> We can do so now either by "blaming" one and finding the originating
> commit, or by searching for "support fetching unadvertised objects" (I
> used the same comment everywhere in the commit [1] so that people can do
> this), but I don't know how to enforce this for future work. (We can add
> a special variable, but I think it's unnecessary and we can't enforce
> that people use that new special variable instead of
> GIT_TEST_PROTOCOL_VERSION anyway.)

Yeah, I think we can find them once we know they need fixing. I was more wondering whether we would remember to do so. I.e., is there a way the test suite could remind us when our assumptions change. I can't think of an easy way to do so, though.

-Peff
Previous: Jonathan TanNext: Junio C Hamano
Message 9 of 26 in “Resend of GIT_TEST_PROTOCOL_VERSION patches”
  1. 0/8 Resend of GIT_TEST_PROTOCOL_VERSION patchesJonathan Tan, Feb 6, 2019
  2. 1/8 tests: define GIT_TEST_PROTOCOL_VERSIONJonathan Tan, Feb 6, 2019
  3. Ævar Arnfjörð BjarmasonFeb 6, 2019
  4. Jonathan TanFeb 7, 2019
  5. Jeff KingFeb 11, 2019
  6. 2/8 tests: always test fetch of unreachable with v0Jonathan Tan, Feb 6, 2019
  7. Jeff KingFeb 11, 2019
  8. Jonathan TanFeb 14, 2019
  9. Jeff KingFeb 21, 2019
  10. Junio C HamanoFeb 22, 2019
  11. Jeff KingFeb 23, 2019
  12. 3/8 t5503: fix overspecification of trace expectationJonathan Tan, Feb 6, 2019
  13. 4/8 t5512: compensate for v0 only sending HEAD symrefsJonathan Tan, Feb 6, 2019
  14. 5/8 t5700: only run with protocol version 1Jonathan Tan, Feb 6, 2019
  15. 6/8 tests: fix protocol version for overspecificationsJonathan Tan, Feb 6, 2019
  16. 7/8 t5552: compensate for v2 filtering ref adv.Jonathan Tan, Feb 6, 2019
  17. 8/8 remote-curl: in v2, fill credentials if neededJonathan Tan, Feb 6, 2019
  18. Jeff KingFeb 6, 2019
  19. Jonathan TanFeb 11, 2019
  20. Jeff KingFeb 11, 2019
  21. Jeff KingFeb 6, 2019
  22. Ævar Arnfjörð BjarmasonFeb 6, 2019
  23. Jeff KingFeb 6, 2019
  24. Ævar Arnfjörð BjarmasonFeb 6, 2019
  25. Jeff KingFeb 6, 2019
  26. Ævar Arnfjörð BjarmasonFeb 7, 2019

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.