git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <rsbecker@nexbridge.com>
To: <git@vger.kernel.org>
Subject: [Test Breakage 2.46.0-rc0] Test t4135.06 fails on NonStop
Date: Sat, 13 Jul 2024 12:41:31 -0400	[thread overview]
Message-ID: <024201dad543$877221e0$965665a0$@nexbridge.com> (raw)

Here is the breakage. This looks like a non-portable dependency on /dev/zero
was introduced.

expecting success of 4153.6 '--reject overrides --no-reject':
        rm -fr .git/rebase-apply &&
        git reset --hard &&
        git checkout first &&
        rm -f file.rej &&

        test_must_fail git am --no-reject side1.eml &&
        test_path_is_dir .git/rebase-apply &&
        test_path_is_missing file.rej &&

        test_must_fail git am --retry --reject </dev/zero &&
        test_path_is_dir .git/rebase-apply &&
        test_path_is_file file.rej

+ rm -fr .git/rebase-apply
+ git reset --hard
HEAD is now at 4f3810f side2
+ git checkout first
Warning: you are leaving 2 commits behind, not connected to
any of your branches:

  4f3810f side2
  deca85c side1

If you want to keep them by creating a new branch, this may be a good time
to do so with:

 git branch <new-branch-name> 4f3810f

HEAD is now at 3aaf771 first
+ rm -f file.rej
+ test_must_fail git am --no-reject side1.eml
Applying: side1
error: patch failed: file:1
error: file: patch does not apply
Patch failed at 0001 side1
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am
--abort".
hint: Disable this message with "git config advice.mergeConflict false"
+ test_path_is_dir .git/rebase-apply
+ test_path_is_missing file.rej
+ test_must_fail git am --retry --reject
+ test_eval_inner_[6]: /dev/zero: cannot open
error: last command exited with $?=1
not ok 6 - --reject overrides --no-reject
#
#               rm -fr .git/rebase-apply &&
#               git reset --hard &&
#               git checkout first &&
#               rm -f file.rej &&
#
#               test_must_fail git am --no-reject side1.eml &&
#               test_path_is_dir .git/rebase-apply &&
#               test_path_is_missing file.rej &&
#
#               test_must_fail git am --retry --reject </dev/zero &&
#               test_path_is_dir .git/rebase-apply &&
#               test_path_is_file file.rej
#
1..6

--
Brief whoami: NonStop&UNIX developer since approximately
UNIX(421664400)
NonStop(211288444200000000)
-- In real life, I talk too much.




             reply	other threads:[~2024-07-13 16:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-13 16:41 rsbecker [this message]
2024-07-14  2:23 ` [Test Breakage 2.46.0-rc0] Test t4135.06 fails on NonStop Junio C Hamano
2024-07-14  7:05   ` Jeff King
2024-07-14 13:36     ` rsbecker
2024-07-17  7:00     ` [PATCH] t4153: stop redirecting input from /dev/zero Jeff King
2024-07-17 13:11       ` rsbecker
2024-07-17 15:35       ` Junio C Hamano
2024-07-14 13:25   ` [Test Breakage 2.46.0-rc0] Test t4135.06 fails on NonStop rsbecker

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='024201dad543$877221e0$965665a0$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=git@vger.kernel.org \
    /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).