From: Eric Sunshine <sunshine@sunshineco.com>
To: Edwin Fernando <edwinfernando734@gmail.com>
Cc: git@vger.kernel.org, Andrei Rybak <rybak.a.v@gmail.com>
Subject: Re: [GSOC][PATCH v4] t3701: don't lose "git" exit codes in test scripts
Date: Mon, 3 Apr 2023 13:03:56 -0400 [thread overview]
Message-ID: <CAPig+cTsqucz0K3e-n0nuu8B87Voaumq9+vtFz0OUCyktszGuA@mail.gmail.com> (raw)
In-Reply-To: <CAPNJDgeHTpoU_eCPPL-adT7R112SyoBdwJF+RbZR6fPPKqSkMg@mail.gmail.com>
On Mon, Apr 3, 2023 at 5:35 AM Edwin Fernando
<edwinfernando734@gmail.com> wrote:
> On Mon, 3 Apr 2023 at 07:25, Eric Sunshine <sunshine@sunshineco.com> wrote:
> > However, it's not clear what breakage you are seeing. In my testing, I
> > don't see any failures, either in a9f4a01760 or after applying your
> > patch to "master". Can you provide more information about the failure
> > you're experiencing?
>
> I cloned git again, ran "make" and all the tests in t3701 passed. The
> local repository I have been working on so far still gives the same error
> though. The error message is not very helpful so I haven't included it. I
> ran "make" on the faulty repository and the tests passed this time. So I
> think the problem was that whatever "make" does was not up to date.
> Also please ignore some mails you may have received because of
> misconfiguration.
That makes sense. An outdated build could indeed account for an
unexpected test failure.
prev parent reply other threads:[~2023-04-03 17:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 17:31 [GSOC][PATCH 0/1] Avoid suppression of git's exit code in tests Edwin Fernando
2023-03-26 17:31 ` [GSOC][PATCH 1/1] t3701: Avoid suppression of exit status of git Edwin Fernando
2023-03-26 20:14 ` Andrei Rybak
2023-03-27 10:11 ` Eric Sunshine
2023-04-01 19:47 ` [GSOC][PATCH v2] t3701: don't lose "git" exit codes in test scripts Edwin Fernando
2023-04-02 10:41 ` Andrei Rybak
2023-04-02 11:36 ` [GSOC][PATCH v3] " Edwin Fernando
2023-04-02 17:17 ` Eric Sunshine
2023-04-02 19:17 ` [GSOC][PATCH v4] " Edwin Fernando
2023-04-03 6:24 ` Eric Sunshine
2023-04-03 9:21 ` Edwin Fernando
2023-04-03 9:34 ` Edwin Fernando
2023-04-03 17:03 ` Eric Sunshine [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
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=CAPig+cTsqucz0K3e-n0nuu8B87Voaumq9+vtFz0OUCyktszGuA@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=edwinfernando734@gmail.com \
--cc=git@vger.kernel.org \
--cc=rybak.a.v@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).