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

Re: [PATCH v2 6/7] Fix tests under GETTEXT_POISON on git-remote

From
Jiang Xin <worldhello.net@gmail.com>
Date
Aug 27, 2012, 21:25 UTC
Message-ID
<CANYiYbGudJ56j=o5SDJur2dv2=icCe2FYad88dV_5tBzLAbZnA@mail.gmail.com>
In-Reply-To
<7v4nnoti3l.fsf@alter.siamese.dyndns.org>
2012/8/28 Junio C Hamano <gitster@pobox.com>:
Show 30 quoted lines
> Jiang Xin <worldhello.net@gmail.com> writes:
>
>> Use i18n-specific test functions in test scripts for git-remote.
>> This issue was was introduced in v1.7.10-233-gbb16d5:
>>
>>     bb16d5 i18n: remote: mark strings for translation
>>
>> and been broken under GETTEXT_POISON=YesPlease since.
>>
>> Signed-off-by: Jiang Xin <worldhello.net@gmail.com>
>> Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
>> ---
>> ...
>> @@ -77,6 +75,14 @@ test_expect_success 'add another remote' '
>>  )
>>  '
>>
>> +test_expect_success C_LOCALE_OUTPUT 'add another remote' '
>> +(
>> +     cd test &&
>> +     check_remote_track origin master side &&
>> +     check_remote_track second master side another &&
>> +)
>> +'
>
> This couldn't have possibly passed with the trailing &&, or am I
> missing something?  There is already "add another remote" before
> this test that adds "second" remote.  Is this test about "add
> yet another remote", or is it checking the result of adding "second"
> that was done in the previous step?

The trailing "&&“ is a copy & paste error. I only run my fixup in GIT_GETTEXT_POISON mode in a harry, not noticed the bypassed testcase has this serious bug.

I split the original "add another remote" into two blocks. One is a normal testcase, and another has a C_LOCALE_OUTPUT prereq flag. This is because other testcases depend on the operations in "add another remote" testcase ('git remote add -f second ../two'), and these testcases would fail if add C_LOCALE_OUTPUT prereq to the whole "add another remote" testcase.

Show 5 quoted lines
>
> Will queue with an obvious fix-up with retitle, 'check tracking', or
> something.
>
> Thanks.
-- 
蒋鑫

北京群英汇信息技术有限公司
邮件: worldhello.net@gmail.com
网址: http://www.ossxp.com/
博客: http://www.worldhello.net/
微博: http://weibo.com/gotgit/
电话: 010-51262007, 18601196889
Previous: Junio C HamanoNext: Junio C Hamano
Message 25 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.