tests: fix test_exceptions

[dtrifiro]

Due to changes in rich 11.1.0, all text formatted using rich.syntax.Syntax is now left-justified (see 0a37fcc),
resulting in output padded with whitespace to the size of the tty.

This resulted in broken tests due to mismatching whitespace between actual dvc.ui output and test cases.

Stripping whitespace in the ui output in test_exceptions solves the broken tests for both rich 11.1.0 and 11.0.0

fixes #7322

[skshetry]

Let's use splitlines, and not use rstrip() in the expected value. Also rstrip defaults to ascii whitespace.

Suggested change

	for l_expected, l_err in zip(expected.split("\n"), err.split("\n")):
	assert l_expected.rstrip(" ") == l_err.rstrip(" ")
	for l_expected, l_err in zip(expected.splitlines(), err.splitlines()):
	assert l_expected == l_err.rstrip()

You may however need to fix some examples.

[skshetry]

Few nitpicky suggestions:

1. I prefer _line suffix than l_ prefix.
2. Keep expected value on the right hand side. (That's fine I think).

Suggested change

	for l_expected, l_err in zip(expected.split("\n"), err.split("\n")):
	assert l_expected.rstrip(" ") == l_err.rstrip(" ")
	for expected_line, err_line in zip(expected.splitlines(), err.splitlines()):
	assert expected_line == err_line.rstrip()

But no strong opinion, just being nitpicky here.

[dtrifiro]

Note that using rstrip() instead of rstrip(" ") will also strip newlines

[skshetry]

Note that using rstrip() instead of rstrip(" ") will also strip newlines

@dtrifiro, sorry, you are right. I was confusing it with bytes.rstrip() for some reason.

[skshetry]

Suggested change

	extra keys not allowed, in stages -> stage1 -> outs -> 0 -> logs ->\n\
	extra keys not allowed, in stages -> stage1 -> outs -> 0 -> logs ->

[skshetry]

Does this fit on a single line now?

Suggested change

	Found duplicate key "cmd" with value "python train.py" (original value:\
	Found duplicate key "cmd" with value "python train.py" (original value: "python

[skshetry]

Probably linters will complain though, black does not for some reason, hmm.

[skshetry]

Similarly, if python moves above, this could be written as:

Suggested change

	"python\ntrain.py"), in line 4, column 5
	train.py"), in line 4, column 5

[skshetry]

Thank you so much @dtrifiro for the quickfix. 🙂