Test_descrtut is driving me up the wall (or actually, the whole test suite is:-). If I run it from regrtest it fails with the completely useless message test_descrtut The actual stdout doesn't match the expected stdout. This much did match (between asterisk lines): ********************************************************************** test_descrtut ********************************************************************** Then ... We expected (repr): '' But instead we got: '*****************************************************************\n' test test_descrtut failed -- Writing: '*****************************************************************\n', expected: '' If I run it standalone it doesn't work because all the typenames are different. This is a general problem, I've seen the same on unix. In general, I find the new test framework not much of an improvement. Whereas with old tests you would get some indication as to what was failing, currently it is at best a not very helpful "We expected '' But in stead we got 'TestFailed'", and at worst something like the above. -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.cwi.nl/~jack | ++++ see http://www.xs4all.nl/~tank/ ++++
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4