From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: Jeff Hostetler <git@jeffhostetler.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Jeff Hostetler <jeffhostetler@github.com>,
edecosta@mathworks.com, git@vger.kernel.org
Subject: Re: [CI]: Is t7527 known to be flakey?
Date: Wed, 25 Jan 2023 22:12:44 +0100 [thread overview]
Message-ID: <20230125211244.GC2155@szeder.dev> (raw)
In-Reply-To: <7fa84280-db1d-8618-571a-ce0ac7a26135@jeffhostetler.com>
On Wed, Jan 25, 2023 at 02:02:40PM -0500, Jeff Hostetler wrote:
> Can you tell from your stess test whether the fsmonitor-daemon
> is crashing? (It might be subtle since the daemon is auto-started
> if necessary, so it might be crashing and silently getting restarted
> by the next command.)
>
> I ask because a SIGPIPE in the client would make me think that the
> server suddenly closed the connection unexpectedly, like if it had
> SIGSEGV'd or something.
Last time around I only looked at the failing test case, and didn't
notice anything that might have indicated the cause of the SIGPIPE.
This time I chanced to look a bit further up in the test log, and:
expecting success of 7527.55 'Matrix[uc:true][fsm:true] move_directory_contents_deeper':
matrix_clean_up_repo &&
$fn &&
if test $uc = false && test $fsm = false
then
git status --porcelain=v1 >.git/expect.$fn
else
git status --porcelain=v1 >.git/actual.$fn &&
test_cmp .git/expect.$fn .git/actual.$fn
fi
+ matrix_clean_up_repo
+ git reset --hard HEAD
HEAD is now at 1d1edcb initial
+ git clean -fd
+ move_directory_contents_deeper
+ mkdir T1/_new_
+ mv T1/F1 T1/F2 T1/T2 T1/_new_
+ test true = false
+ git status --porcelain=v1
error: read error: Connection reset by peer
error: could not read IPC response
+ test_cmp .git/expect.move_directory_contents_deeper .git/actual.move_directory_contents_deeper
+ test 2 -ne 2
+ eval diff -u "$@"
+ diff -u .git/expect.move_directory_contents_deeper .git/actual.move_directory_contents_deeper
ok 55 - Matrix[uc:true][fsm:true] move_directory_contents_deeper
expecting success of 7527.56 'Matrix[uc:true][fsm:true] move_directory_up':
matrix_clean_up_repo &&
$fn &&
if test $uc = false && test $fsm = false
then
git status --porcelain=v1 >.git/expect.$fn
else
git status --porcelain=v1 >.git/actual.$fn &&
test_cmp .git/expect.$fn .git/actual.$fn
fi
+ matrix_clean_up_repo
+ git reset --hard HEAD
HEAD is now at 1d1edcb initial
+ git clean -fd
Removing T1/_new_/
+ move_directory_up
+ mv T1/T2/T3 T1
+ test true = false
+ git status --porcelain=v1
error: last command exited with $?=141
not ok 56 - Matrix[uc:true][fsm:true] move_directory_up
Notice that "error: read error: Connection reset by peer" in the
previous, still successful test case! I ran it a couple of times, and
saw the same error message in the still successful '42 -
Matrix[uc:false][fsm:true] move_directory_contents_deeper' followed by
a SIGPIPE caused failure in the next test case. And now that I knew
what to look for, I noticed this error message in the very first test
failure I reported the other day, which didn't fail because of
SIGPIPE, and in that case the error message was printed in the failed
test case.
And there were a few cases that failed because of SIGPIPE but there
were no error messages at all.
I can't say what caused these errors, but I doubt that anything
segfaulted, because segfaults are logged in syslog, and I haven't
found any such syslog entries coinciding with stress testing.
prev parent reply other threads:[~2023-01-25 21:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 2:52 [CI]: Is t7527 known to be flakey? Junio C Hamano
2023-01-20 15:23 ` Jeff Hostetler
2023-01-20 15:40 ` Junio C Hamano
2023-01-21 10:23 ` SZEDER Gábor
2023-01-23 16:56 ` Jeff Hostetler
2023-01-23 18:12 ` SZEDER Gábor
2023-01-25 19:02 ` Jeff Hostetler
2023-01-25 21:12 ` SZEDER Gábor [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=20230125211244.GC2155@szeder.dev \
--to=szeder.dev@gmail.com \
--cc=edecosta@mathworks.com \
--cc=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jeffhostetler@github.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).