Source: mailman3
Version: 3.3.10-2
Severity: important
I'd like to upload flufl.bounce 5.x to unstable, because it will fix
https://bugs.debian.org/1083397. However, in
https://debusine.debian.net/debian/developers/work-request/936438/ I
found that this makes mailman3's autopkgtests worse. It wouldn't
technically prevent testing migration since mailman3's autopkgtests are
already failing in testing (#XXX), but I'd rather get it fixed anyway.
The new test failures are:
======================================================================
FAIL: test_subscription_pending
(mailman.commands.tests.test_cli_syncmembers.TestCLISyncMembers.test_subscription_pending)
----------------------------------------------------------------------
Traceback (most recent call last):
File
"/tmp/autopkgtest.F76XuB/build.UOg/src/src/mailman/commands/tests/test_cli_syncmembers.py",
line 130, in test_subscription_pending
self.assertEqual(result.output,
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^
'[ADD] Anne Person'
^^^^^^^^^^^^^^^^^^^
...<3 lines>...
'[ADD] Bart Person'
^^^^^^^^^^^^^^^^^^^
' <[email protected]>\n')
^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: '[ADD[32 chars]om>\n[ADD] Bart Person
<[email protected]>\n[72 chars]m>\n' != '[ADD[32 chars]om>\nSubscription
already pending (skipping): [72 chars]m>\n'
[ADD] Anne Person <[email protected]>
+ Subscription already pending (skipping): Anne Person <[email protected]>
[ADD] Bart Person <[email protected]>
- Subscription already pending (skipping): Anne Person <[email protected]>
======================================================================
FAIL: test_sync_empty_tuple
(mailman.commands.tests.test_cli_syncmembers.TestCLISyncMembers.test_sync_empty_tuple)
----------------------------------------------------------------------
Traceback (most recent call last):
File
"/tmp/autopkgtest.F76XuB/build.UOg/src/src/mailman/commands/tests/test_cli_syncmembers.py",
line 99, in test_sync_empty_tuple
self.assertEqual(result.output, "Cannot parse as valid email "
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"address (skipping): \"\"\n"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"[DEL] Bart Person "
^^^^^^^^^^^^^^^^^^^^
"<[email protected]>\n")
^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: '[DEL] Bart Person <[email protected]>\n[48 chars]""\n' !=
'Cannot parse as valid email address (skip[48 chars]m>\n'
+ Cannot parse as valid email address (skipping): ""
[DEL] Bart Person <[email protected]>
- Cannot parse as valid email address (skipping): ""
======================================================================
FAIL: test_sync_invalid_email
(mailman.commands.tests.test_cli_syncmembers.TestCLISyncMembers.test_sync_invalid_email)
----------------------------------------------------------------------
Traceback (most recent call last):
File
"/tmp/autopkgtest.F76XuB/build.UOg/src/src/mailman/commands/tests/test_cli_syncmembers.py",
line 72, in test_sync_invalid_email
self.assertEqual(
~~~~~~~~~~~~~~~~^
result.output,
^^^^^^^^^^^^^^
...<3 lines>...
' (skipping): not-a-valid@email\n'
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
'Nothing to do\n')
^^^^^^^^^^^^^^^^^^
AssertionError: 'Nothing to do\nCannot parse as valid emai[121 chars]il\n' !=
'Cannot parse as valid email address (skip[121 chars]do\n'
- Nothing to do
Cannot parse as valid email address (skipping): Dont Subscribe
<not-a-valid-email>
Cannot parse as valid email address (skipping): not-a-valid@email
+ Nothing to do
Thanks,
--
Colin Watson (he/him) [[email protected]]
