From: Junio C Hamano <gitster@pobox.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: GIT Mailing-list <git@vger.kernel.org>
Subject: Re: t9001 failures on 32-bit Linux?
Date: Sun, 10 Dec 2017 14:28:07 -0800 [thread overview]
Message-ID: <xmqqfu8i5ibs.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <42367c9f-debb-8ea2-e1ea-1ca513853ded@ramsayjones.plus.com> (Ramsay Jones's message of "Sun, 10 Dec 2017 19:58:18 +0000")
Ramsay Jones <ramsay@ramsayjones.plus.com> writes:
> Hi Junio,
>
> I noticed the revert of the 'ab/simplify-perl-makefile' branch on
> top of 'pu'. So, I fired up my 32-bit Linux and attempted to see
> if I could debug this t9001 test failure.
>
> Unfortunately, I could not get it to fail. :(
>
> Both of the 'pu' (@77e921d77d) and 'pu~1' (@cfef1ebefd) builds pass
> the full test-suite and, likewise, running t9001 in a loop for a
> count of 100 (about 45 minutes run-time each).
>
> [If it makes any difference, I don't have sendmail installed (no
> /usr/sbin/sendmail or /usr/lib/sendmail), or any sendmail in my
> $PATH.]
>
> Sorry I couldn't help with this! :(
I suspect that the difference is not about send(e)mail per-se, but
the differences between the set of perl modules installed in the
linux32 Travis environment and the other one. Perhaps the use of
deprecated Error.pm is the culprit?
I do appreciate that the environments we use on Travis are not
monoculture and we end up testing more variations (in this case,
the cause likely does not have anything to do with 64- vs 32-bit,
but Perl modules). It sometimes gets confusing, though ;-)
Another difference I noticed while scanning the failing log is that
the Linux32 environment seem to lack libsvn-perl and all tests are
skipped there. I do not think that this particular variation is
helping us to diversify our test base, though ;-)
Thanks.
prev parent reply other threads:[~2017-12-10 22:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-10 19:58 t9001 failures on 32-bit Linux? Ramsay Jones
2017-12-10 20:33 ` Ævar Arnfjörð Bjarmason
2017-12-10 21:02 ` Ramsay Jones
2017-12-10 21:14 ` Ævar Arnfjörð Bjarmason
2017-12-10 22:28 ` Junio C Hamano [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=xmqqfu8i5ibs.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ramsay@ramsayjones.plus.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).