pystache: FTBFS: Tests failed

Imported from Debian bug http://bugs.debian.org/735833:

Source: pystache
Version: 0.5.3-2
Severity: serious
Tags: jessie sid
User: <email address hidden>
Usertags: qa-ftbfs-20140114 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory `/«PKGBUILDDIR»'
> nosetests -d build2 && \
> nosetests3 -d build3
>
> ----------------------------------------------------------------------
> Ran 0 tests in 0.000s
>
> OK
> ......................................................................................................................................................................................................F......................................................
> ======================================================================
> FAIL: Test that the decode_errors attribute is respected.
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File "/«PKGBUILDDIR»/build3/lib/pystache/tests/test_renderer.py", line 222, in test_unicode__decode_errors
> self.assertEqual(renderer.str(b), 'd\\ufffd\\ufffdf')
> nose.proxy.AssertionError: 'd\ufffd\ufffdf' != 'd\\ufffd\\ufffdf'
> - d\ufffd\ufffdf
> + d\ufffd\ufffdf
>
> """Fail immediately, with the given message."""
> >> raise self.failureException("'d\ufffd\ufffdf' != 'd\\\\ufffd\\\\ufffdf'\n- d\ufffd\ufffdf\n+ d\\ufffd\\ufffdf\n")
>
>
> ----------------------------------------------------------------------
> Ran 253 tests in 0.398s
>
> FAILED (failures=1)
> make[1]: *** [override_dh_auto_test] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/01/14/pystache_0.5.3-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.