From 655a4dbc36d95ce4a82cbc13aa9e2002b41fa4de Mon Sep 17 00:00:00 2001 From: Chris Wilson Date: Mon, 13 Jul 2009 14:31:43 +0100 Subject: [test] Track XFAIL using expected results stored as xfail.png Instead of tagging the sources, which is insensitive to changes, track the known failure modes by recording the current fail as an xfail.png reference. (We also introduce a new.png to track a fresh error, so that they are not lost in the noise of the old XFAILs and hopefully do not cause everyone to fret). As we have removed the XFAIL tagging we find, surprise surprise, that some tests are now working -- so review all the reference images (as also some .ref.png now should be .xfail.png). Note: I've only checked image,pdf,ps,svg. The test surfaces report some failures that probably need to addressed in source. I've not correct the changes for win32 and quartz. Nor fixed up the experimental backends. --- test/extend-pad.svg.xfail.png | Bin 0 -> 270 bytes 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 test/extend-pad.svg.xfail.png (limited to 'test/extend-pad.svg.xfail.png') diff --git a/test/extend-pad.svg.xfail.png b/test/extend-pad.svg.xfail.png new file mode 100644 index 000000000..a2cf3530c Binary files /dev/null and b/test/extend-pad.svg.xfail.png differ -- cgit v1.2.3