to XFAIL or not to XFAIL

[Doug Evans]

DJ Delorie writes:
 > If we had a third case, say KFAIL, for "known to fail but ignore it
 > anyway," I'd be happy to go along with your policy.  Using XFAIL for
 > both "ignore until later" and "impossible to fix on this target" makes
 > it difficult to assess the overall quality of the software.

For the "impossible to fix on this target" case, how about either
a) not run the test on the particular target, or
b) mark the test as UNSUPPORTED (which already exists), not XFAIL.

To me, that is better than adding a new "KFAIL".