smoketest: T3871: discard staged changes after an expected commit failure

Two ethtool test cases intentionally trigger a commit failure for an
unsupported driver, then move on to the next interface in the same loop.
Commit does not auto-rollback on failure and the session is shared across
the loop, so the failed change stayed staged and could silently carry into
the next interface's commit - failing an otherwise passing interface if it
followed an unsupported one. Discard the candidate configuration right
after each expected failure, matching the pattern already used elsewhere in
the suite.

Assisted-by: Claude:claude-sonnet-5

0 files changed, 0 insertions, 0 deletions