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

Re: [PATCH] t3419: prevent failure when run with EXPENSIVE

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 20, 2020, 22:24 UTC
Message-ID
<xmqqeetmbr6z.fsf@gitster.c.googlers.com>
In-Reply-To
<CABPp-BGiP7eG7Ojt8FKV5PUBFk74pkO6jnOwJEZbDzBjdJUm5w@mail.gmail.com>
Elijah Newren <newren@gmail.com> writes:
Show 9 quoted lines
>> -               rm -rf .git/rebase-apply
>> +               rm -rf .git/rebase-merge .git/rebase-apply
>>         '
>>  }
>
> Good catch, thanks.  Perhaps we just want to invoke 'git rebase
> --quit' and let it clean up instead of manually doing so ourselves,
> since it may buy us some future-proofing in case we ever want to move
> the place we store rebase state?

I started writing "I would agree 100% if this script were not about testing 'rebase', but using 'rebase' itself for a framework to test 'rebase'???" but then if 'rebase --quit' fails to clear these, what we are likely to see is that the next test to fail, so it probably is an OK approach.

Thanks.
Previous: brian m. carlsonNext: brian m. carlson
Message 4 of 8 in “t3419: prevent failure when run with EXPENSIVE”
  1. t3419: prevent failure when run with EXPENSIVEbrian m. carlson, Mar 20, 2020
  2. Elijah NewrenMar 20, 2020
  3. brian m. carlsonMar 20, 2020
  4. Junio C HamanoMar 20, 2020
  5. t3419: prevent failure when run with EXPENSIVEbrian m. carlson, Mar 20, 2020
  6. t3419: drop EXPENSIVE testsJeff King, Mar 22, 2020
  7. brian m. carlsonMar 22, 2020
  8. Jeff KingMar 22, 2020

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.