delete minor unreachable code caused by t.FailNow

[Abirdcfly]

Signed-off-by: Abirdcfly fp544037857@gmail.com

Initial Checklist

• There is an issue describing the need for this PR.
• Git log contains summary of the change.
• Git log contains motivation and context of the change.
• If part of an EPIC, PR git log contains EPIC number.
• If part of an EPIC, PR was added to EPIC description.

Description (git log)

delete minor unreachable code caused by t.FailNow

Fixes: #issue_number

Type of change

• Bug fix (non-breaking change fixing an issue, preferable).
• Quick fix (minor non-breaking change requiring no issue, use with care)
• Code refactor (code improvement and/or code removal)
• New feature (non-breaking change adding functionality).
• Breaking change (cause existing functionality not to work as expected).

How Has This Been Tested?

see https://go.dev/play/p/3AtpQLkd8t- for example:

package main

import (
	"testing"
)

func TestLastIndex(t *testing.T) {
	t.Errorf("this line will print and exit")
	t.FailNow()
	t.Errorf("this line can't print")
}

/* output:
=== RUN   TestLastIndex
    prog.go:8: this line will print and exit
--- FAIL: TestLastIndex (0.00s)
FAIL

Program exited.
*/

Tests being included in this PR:

• Test File A
• Test File B

Reproduce the test by running:

• command 01
• command 02

Final Checklist:

Pick "Bug Fix" or "Feature", delete the other and mark appropriate checks.

• I have made corresponding changes to the documentation.
• My code follows the style guidelines (C and Go) of this project.
• I have performed a self-review of my own code.
• I have commented all functions/methods created explaining what they do.
• I have commented my code, particularly in hard-to-understand areas.
• My changes generate no new warnings.
• I have added tests that prove my fix, or feature, is effective.
• New and existing unit tests pass locally with my changes.
• Any dependent changes have been merged and published before.

Git Log Checklist:

My commits logs have:

• Subject starts with "subsystem|file: description".
• Do not end the subject line with a period.
• Limit the subject line to 50 characters.
• Separate subject from body with a blank line.
• Use the imperative mood in the subject line.
• Wrap the body at 72 characters.
• Use the body to explain what and why instead of how.

[CLAassistant]

All committers have signed the CLA.

[rafaeldtinoco]

@Abirdcfly, thanks for your contribution. I need you to sign the CLA in order to merge this fix.

[NDStrahilevitz]

LGTM