On Mon, Feb 06 2023, Shuqi Liang wrote: > On Mon, Feb 6, 2023 at 5:44 PM Junio C Hamano <gitster@xxxxxxxxx> wrote: > >> Have you run the resulting test? > > My apologies for not testing after V1. That was a major oversight on > my part. I'll make sure to thoroughly test before each submission to > avoid any issues with the code in the future. > > >> This creates a "test-patch" file with lines 'a' and 'b' that are >> common context lines without any whitespace before them, no? The >> original left the necessary single space in front of them (see the >> line removed above). > > I try to change the code to(left the necessary single space in front > of 'a' and 'b': > > diff --git a/t/t4113-apply-ending.sh b/t/t4113-apply-ending.sh > index ab5ecaab7f..ef61a3187c 100755 > --- a/t/t4113-apply-ending.sh > +++ b/t/t4113-apply-ending.sh > @@ -14,8 +14,8 @@ test_expect_success setup ' > --- a/file > +++ b/file > @@ -1,2 +1,3 @@ > - a > - b > + a > + b > +c > EOF > > Here I only show one part ,but I fix two same issue in the V4 patch > and it still can not pass the test . > It say : > > Test Summary Report > > ------------------- > > t4113-apply-ending.sh (Wstat: 256 Tests: 0 Failed: 0) > > Non-zero exit status: 1 > > Parse errors: No plan found in TAP output > > Files=1, Tests=0, 0 wallclock secs ( 0.01 usr 0.01 sys + 0.05 cusr > 0.02 csys = 0.09 CPU) > > Result: FAIL. > > I'm stumped as to why it's still failing. I've tried searching for > answers on StackOverflow, but I still can't figure it out. > ---------------- > Thanks, > Shuqi The error doesn't tell us much, instead of "make prove" or "prove <name>" running e.g.: ./t4113-apply-ending.sh -vixd Gives you better output. But this is almost certainly that you're trying to insert leading whitespace into a line that's in a <<-EOF here-doc, the "-" part of that means that your leading whitespace is being stripped. A typical idiom for that is have a marker for the start of line, and strip the whitespace with "sed". See this for existing examples: git grep 'sed.*\^.*>.*EOF'
