* CI fail: "invalid object type" only on dockerized linux32 runs?
@ 2021-05-25 21:22 Junio C Hamano
2021-05-26 11:53 ` Ævar Arnfjörð Bjarmason
0 siblings, 1 reply; 2+ messages in thread
From: Junio C Hamano @ 2021-05-25 21:22 UTC (permalink / raw)
To: git; +Cc: Ævar Arnfjörð Bjarmason
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?
Thanks.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: CI fail: "invalid object type" only on dockerized linux32 runs?
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
0 siblings, 0 replies; 2+ messages in thread
From: Ævar Arnfjörð Bjarmason @ 2021-05-26 11:53 UTC (permalink / raw)
To: Junio C Hamano; +Cc: git
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...
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-05-26 11:55 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 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).