backintime 1.2.0-5.fc31 fails to build with Python 3.8.0a4+: =================================== FAILURES =================================== ________________________ TestBackInTime.test_quiet_mode ________________________ self = <test.test_backintime.TestBackInTime testMethod=test_quiet_mode> def test_quiet_mode(self): > self.assertEquals("", subprocess.getoutput("python3 backintime.py --quiet")) E AssertionError: '' != '/usr/lib64/python3.8/site-packages/dbus/c[301 chars]gnal' E + /usr/lib64/python3.8/site-packages/dbus/connection.py:335: SyntaxWarning: invalid escape sequence \ E + """Arrange for the given function to be called when a signal matching E + /usr/lib64/python3.8/site-packages/dbus/proxies.py:305: SyntaxWarning: invalid escape sequence \ E + """Arrange for the given function to be called when the given signal test/test_backintime.py:33: AssertionError Full logs in https://copr.fedorainfracloud.org/coprs/g/python/python3.8/build/914372/
Obviously, another issue with the changed API of the subprocess module. There's also a deprecation warning: > /builddir/build/BUILD/backintime-1.2.0/common/test/test_backintime.py:33: DeprecationWarning: Please use assertEqual instead.
The tests use subprocess to check something. And the test expect empty output, however there are SyntaxWarnings. This has nothing to do with the API of the subprocess module. There are 2 ways to fix this: 1) fix the SyntaxWarnings in dbus/connection.py (out of scope of this package, requires coordination) 2) change the test to call self.assertEqual("", subprocess.getoutput("python3 -W ignore::SyntaxWarning backintime.py --quiet")) (self contained)
Thanks for the analysis. We should head for both proposed fixes, because: 1) the warnings can be expected to be printed also to the user while a real backup runs. 2) could be a good workaround for the test at least and can get filed as a patch to upstream.