summaryloggraphiclog1graphiclog2commitcommitdifftreerefseditfork
rawpatchinlineside by side (parent: 8f63910)
rawpatchinlineside by side (parent: 8f63910)
| author | Sven Verdoolaege <sven@cerebras.net> | |
| Thu, 24 Oct 2019 13:46:38 +0000 (24 15:46 +0200) | ||
| committer | Sven Verdoolaege <sven@cerebras.net> | |
| Tue, 14 Feb 2023 21:32:19 +0000 (14 22:32 +0100) |
That is, instead of printing the expected result directly
as the string stored in the test program,
print it in the same way as the obtained result.
In general, this makes it easier to see the difference.
For object types that need to be compared with "plain_is_equal",
it is also important to show the parsed expected result since
that may not be obviously equal to the original string.
Signed-off-by: Sven Verdoolaege <sven@cerebras.net>
as the string stored in the test program,
print it in the same way as the obtained result.
In general, this makes it easier to see the difference.
For object types that need to be compared with "plain_is_equal",
it is also important to show the parsed expected result since
that may not be obviously equal to the original string.
Signed-off-by: Sven Verdoolaege <sven@cerebras.net>
| isl_test2.cc | patchblobblamehistory |
diff --git a/isl_test2.cc b/isl_test2.cc
--- a/isl_test2.cc
+++ b/isl_test2.cc
ss << name << "(" << test.arg1 << ", " << test.arg2 << ") =\n"
<< res << "\n"
<< "expecting:\n"
- << test.res;
+ << expected;
THROW_INVALID(ss.str().c_str());
}
}