From: Junio C Hamano <gitster@pobox.com>
To: ZheNing Hu <adlternative@gmail.com>
Cc: ZheNing Hu via GitGitGadget <gitgitgadget@gmail.com>,
Git List <git@vger.kernel.org>,
Christian Couder <christian.couder@gmail.com>,
Hariom Verma <hariom18599@gmail.com>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: Re: [PATCH 0/4] [GSOC][RFC] ref-filter: add %(rest) atom
Date: Wed, 09 Jun 2021 16:16:34 +0900 [thread overview]
Message-ID: <xmqqzgvzik31.fsf@gitster.g> (raw)
In-Reply-To: <CAOLTT8RURwom91VqFATjMEGGe5NJRgyWSojCC=TH8DwG+7MeSA@mail.gmail.com> (ZheNing Hu's message of "Wed, 9 Jun 2021 11:55:43 +0800")
ZheNing Hu <adlternative@gmail.com> writes:
> It’s worth mentioning that this patch still fails the github CI test. [1]
>
> t6300-for-each-ref.sh:
> 274: Verify sorts with raw
> 275: Verify sorts with raw:size
> 278: empty raw refs with %(if)
>
> There is no such breakage on my local machine.
>
> [1] https://github.com/gitgitgadget/git/pull/976/checks?check_run_id=2774963705
It's one of the two 32-bit jobs, I think. If the other one fails
the same way, that means the code does not work on 32-bit systems,
most likely something in your code assumes certain types are 64-bit
when they aren't.
next prev parent reply other threads:[~2021-06-09 7:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 14:37 [PATCH 0/4] [GSOC][RFC] ref-filter: add %(rest) atom ZheNing Hu via GitGitGadget
2021-06-08 14:37 ` [PATCH 1/4] [GSOC] ref-filter: add obj-type check in grab contents ZheNing Hu via GitGitGadget
2021-06-08 14:38 ` [PATCH 2/4] [GSOC] ref-filter: add %(raw) atom ZheNing Hu via GitGitGadget
2021-06-08 14:38 ` [PATCH 3/4] [GSOC] ref-filter: use non-const ref_format in *_atom_parser() ZheNing Hu via GitGitGadget
2021-06-08 14:38 ` [PATCH 4/4] [GSOC] ref-filter: add %(rest) atom ZheNing Hu via GitGitGadget
2021-06-09 3:39 ` [PATCH 0/4] [GSOC][RFC] " Junio C Hamano
2021-06-09 3:55 ` ZheNing Hu
2021-06-09 7:16 ` Junio C Hamano [this message]
2021-06-09 16:11 ` [PATCH v2 " ZheNing Hu via GitGitGadget
2021-06-09 16:11 ` [PATCH v2 1/4] [GSOC] ref-filter: add obj-type check in grab contents ZheNing Hu via GitGitGadget
2021-06-09 16:11 ` [PATCH v2 2/4] [GSOC] ref-filter: add %(raw) atom ZheNing Hu via GitGitGadget
2021-06-09 16:12 ` [PATCH v2 3/4] [GSOC] ref-filter: use non-const ref_format in *_atom_parser() ZheNing Hu via GitGitGadget
2021-06-09 16:12 ` [PATCH v2 4/4] [GSOC] ref-filter: add %(rest) atom ZheNing Hu via GitGitGadget
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqzgvzik31.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=adlternative@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=hariom18599@gmail.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).