[Ltrace-devel] 0002-Fix-FAIL-in-wchar.exp-test.patch
Ivan Zakharyaschev
imz at altlinux.org
Thu Nov 23 10:26:09 UTC 2017
(Sorry, I missed the correct patch which I am commenting in the previous
message. It also had a wrong title. Now I'm correcting this by repeating
that message with the right subject and the discussed patch included.)
Hello!
It would be more natural just to declare this test (of a feature which has
not yet been implemented) as "X-FAIL"; I mean: which is expected to fail.
It will always be run, and in future, if something changes, we'll notice
the change in the test results and act
accordingly.
Does the testing system (dejagnu?) has a way to say that a test is
expected not to pass, but to fail (and not count it as a real failure)?
(A switch like a define is better suited to reflect the features of the
environment, external to our project; as an advice for the other patch:
perhaps, whether we have the debuginfo for glibc available could be
reflected by a "switch".)
--
Best regards,
Ivan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-Fix-FAIL-in-wchar.exp-test.patch
Type: text/x-patch
Size: 3859 bytes
Desc:
URL: <http://lists.alioth.debian.org/pipermail/ltrace-devel/attachments/20171123/f9d76491/attachment-0001.bin>
More information about the Ltrace-devel
mailing list