From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: CI fail: "invalid object type" only on dockerized linux32 runs?
Date: Wed, 26 May 2021 13:53:11 +0200 [thread overview]
Message-ID: <87k0nln22m.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqsg2acxvo.fsf@gitster.g>
On Wed, May 26 2021, Junio C Hamano wrote:
> https://github.com/git/git/runs/2669078911?check_suite_focus=true#step:6:3195
>
> shows a test that expects "git cat-file: could not get object_info"
> gets "invalid object type". What is curious is that most of the
> other workflow runs do not get this error. Only on the 32-bit run.
>
> Rings any bell?
That's clearly a bug in code I added, but I haven't been able to
reproduce it yet. There's a 32 bit Debian box on the GCC farm that I
tested this on, and there the tests works just fine, odd...
prev parent reply other threads:[~2021-05-26 11:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 21:22 CI fail: "invalid object type" only on dockerized linux32 runs? Junio C Hamano
2021-05-26 11:53 ` Ævar Arnfjörð Bjarmason [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0nln22m.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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 NNTP newsgroup(s).