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

Re: [PATCH 5/7] Fix tests under GETTEXT_POISON on pack-object

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Aug 21, 2012, 14:24 UTC
Message-ID
<20120821142441.GA56154@mannheim-rule.local>
In-Reply-To
<CACsJy8DHdj61sH8DjLsUfKdb4yzbnACWdCsgmFDtjJqq08c2TQ@mail.gmail.com>
Nguyen Thai Ngoc Duy wrote:
> On Tue, Aug 21, 2012 at 12:17 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:
Show 16 quoted lines
>>> @@ -35,7 +35,7 @@ test_expect_success 'upload-pack fails due to error in pack-objects packing' '
>>>       printf "0032want %s\n00000009done\n0000" \
>>>               $(git rev-parse HEAD) >input &&
>>>       test_must_fail git upload-pack . <input >/dev/null 2>output.err &&
>>> -     grep "unable to read" output.err &&
>>> +     test_i18ngrep "unable to read" output.err &&
>>>       grep "pack-objects died" output.err
>>
>> Wouldn't it make sense to change the second "grep" of output intended
>> for humans to test_i18ngrep while at it?
>
> This comes from error("git upload-pack: git-pack-objects died with
> error.") in unpack-trees.c, which is not i18n-ized yet. There's
> another test in t5530 that does the same grep. I think we should leave
> it as is until we mark the string for translation, then gettext poison
> will spot it (verified) and we can fix it.

I don't understand the distinction you're making. Isn't the message intended for humans, and wouldn't changing that one line to test_i18ngrep now save trouble later? Tests are meant to check git's intended behavior, not to exactly match its current behavior.

Jonathan
Previous: Nguyen Thai Ngoc DuyNext: Junio C Hamano
Message 9 of 27 in “Gettext poison fixes”
  1. 0/7 Gettext poison fixesNguyễn Thái Ngọc Duy, Aug 21, 2012
  2. 1/7 Fix tests under GETTEXT_POISON on relative datesNguyễn Thái Ngọc Duy, Aug 21, 2012
  3. 2/7 Fix tests under GETTEXT_POISON on git-stashNguyễn Thái Ngọc Duy, Aug 21, 2012
  4. 3/7 Fix tests under GETTEXT_POISON on diffstatNguyễn Thái Ngọc Duy, Aug 21, 2012
  5. 4/7 Fix tests under GETTEXT_POISON on git-applyNguyễn Thái Ngọc Duy, Aug 21, 2012
  6. 5/7 Fix tests under GETTEXT_POISON on pack-objectNguyễn Thái Ngọc Duy, Aug 21, 2012
  7. Jonathan NiederAug 21, 2012
  8. Nguyen Thai Ngoc DuyAug 21, 2012
  9. Jonathan NiederAug 21, 2012
  10. Junio C HamanoAug 21, 2012
  11. 6/7 Fix tests under GETTEXT_POISON on git-remoteNguyễn Thái Ngọc Duy, Aug 21, 2012
  12. Junio C HamanoAug 21, 2012
  13. Jiang XinAug 22, 2012
  14. Junio C HamanoAug 22, 2012
  15. 7/7 Fix tests under GETTEXT_POISON on parseoptNguyễn Thái Ngọc Duy, Aug 21, 2012
  16. 0/7 Gettext poison fixesJiang Xin, Aug 27, 2012
  17. 1/7 Fix tests under GETTEXT_POISON on relative datesJiang Xin, Aug 27, 2012
  18. 2/7 Fix tests under GETTEXT_POISON on git-stashJiang Xin, Aug 27, 2012
  19. 3/7 Fix tests under GETTEXT_POISON on diffstatJiang Xin, Aug 27, 2012
  20. 4/7 Fix tests under GETTEXT_POISON on git-applyJiang Xin, Aug 27, 2012
  21. 5/7 Fix tests under GETTEXT_POISON on pack-objectJiang Xin, Aug 27, 2012
  22. 6/7 Fix tests under GETTEXT_POISON on git-remoteJiang Xin, Aug 27, 2012
  23. 7/7 Fix tests under GETTEXT_POISON on parseoptJiang Xin, Aug 27, 2012
  24. Junio C HamanoAug 27, 2012
  25. Jiang XinAug 27, 2012
  26. Junio C HamanoAug 28, 2012
  27. Junio C HamanoAug 27, 2012

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.