Source: python-testtools Version: 2.5.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211220 ftbfs-bookworm
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<<PKGBUILDDIR>>' > make[1]: pyversions: No such file or directory > py3versions: no X-Python3-Version in control file, using supported versions > set -ex ; for pyvers in 3.10 3.9; do \ > PYTHONPATH=/<<PKGBUILDDIR>> PYTHON=python$pyvers python$pyvers -m > testtools.run testtools.tests.test_suite ; \ > done > + PYTHONPATH=/<<PKGBUILDDIR>> PYTHON=python3.10 python3.10 -m testtools.run > testtools.tests.test_suite > /usr/lib/python3.10/runpy.py:126: RuntimeWarning: 'testtools.run' found in > sys.modules after import of package 'testtools', but prior to execution of > 'testtools.run'; this may result in unpredictable behaviour > warn(RuntimeWarning(msg)) > Tests running... > ====================================================================== > FAIL: testtools.tests.test_testresult.TestNonAsciiResults.test_syntax_error > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/<<PKGBUILDDIR>>/testtools/tests/test_testresult.py", line 2676, in > test_syntax_error > self.assertIn(self._as_output( > File "/<<PKGBUILDDIR>>/testtools/testcase.py", line 399, in assertIn > self.assertThat(haystack, Contains(needle), message) > File "/<<PKGBUILDDIR>>/testtools/testcase.py", line 480, in assertThat > raise mismatch_error > testtools.matchers._impl.MismatchError: ' File "<string>", line 1\n f(a, > b c)\n ^\nSyntaxError: ' not in 'Tests > running...\n======================================================================\nERROR: > > test_syntax_error.Test.runTest\n----------------------------------------------------------------------\nTraceback > (most recent call last):\n File > "/tmp/TestNonAsciiResults07m6k1o1/test_syntax_error.py", line 6, in runTest\n > exec (\'f(a, b c)\')\n File "<string>", line 1\n f(a, b c)\n > ^^^\nSyntaxError: invalid syntax. Perhaps you forgot a comma?\n\nRan 1 test > in 0.001s\nFAILED (failures=1)\n' > ====================================================================== > FAIL: > testtools.tests.test_testresult.TestNonAsciiResultsWithUnittest.test_syntax_error > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/<<PKGBUILDDIR>>/testtools/tests/test_testresult.py", line 2676, in > test_syntax_error > self.assertIn(self._as_output( > File "/<<PKGBUILDDIR>>/testtools/testcase.py", line 399, in assertIn > self.assertThat(haystack, Contains(needle), message) > File "/<<PKGBUILDDIR>>/testtools/testcase.py", line 480, in assertThat > raise mismatch_error > testtools.matchers._impl.MismatchError: ' File "<string>", line 1\n f(a, > b c)\n ^\nSyntaxError: ' not in > 'E\n======================================================================\nERROR: > runTest > (test_syntax_error.Test)\ntest_syntax_error.Test.runTest\n----------------------------------------------------------------------\ntesttools.testresult.real._StringException: > Traceback (most recent call last):\n File > "/tmp/TestNonAsciiResultsWithUnittestwnxlmk1_/test_syntax_error.py", line 6, > in runTest\n exec (\'f(a, b c)\')\n File "<string>", line 1\n f(a, b > c)\n ^^^\nSyntaxError: invalid syntax. Perhaps you forgot a > comma?\n\n\n----------------------------------------------------------------------\nRan > 1 test in 0.000s\n\nFAILED (errors=1)\n' > > Ran 2625 tests in 0.376s > FAILED (failures=2) > make[1]: *** [debian/rules:36: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/12/20/python-testtools_2.5.0-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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
