Comment 16 for bug 1846787

The remaining autopkgtests regressions (nplan/amd64 and gvfs/s390x) are also unrelated to this change.

- nplan/amd64 passed with 3 retests:

Before:

  test_mix_bridge_on_bond (__main__.TestNetworkManager) ... FAIL
  ...
  integration.py FAIL non-zero exit status 1

After:

  test_mix_bridge_on_bond (__main__.TestNetworkManager) ... ok
  ...
  integration.py PASS

- gvfs/s390x has a long history of flaky/likely failures on these 2 tests, as seen in

  https://autopkgtest.ubuntu.com/packages/gvfs/xenial/s390x

So it is OK to ignore this one, it's not a regression from _this_ change.

Examples:

1.28.2-1ubuntu1~16.04.3 systemd/229-4ubuntu21.23 2019-12-02 13:31:15 UTC 0h 41m 38s mfo fail

  trash:// deletion, attributes, restoring for a file in $HOME (API) ... FAIL
  trash:// deletion, attributes, restoring for a file in $HOME (CLI) ... FAIL

1.28.2-1ubuntu1~16.04.3 systemd/229-4ubuntu21.23 2019-11-27 22:19:05 UTC 0h 02m 29s ddstreet fail

  trash:// deletion, attributes, restoring for a file in $HOME (API) ... ok
  trash:// deletion, attributes, restoring for a file in $HOME (CLI) ... FAIL

with a previous, anecdotal entry of 6 retests until passing on:

1.28.2-1ubuntu1~16.04.2 apache2/2.4.18-2ubuntu3.9 2018-06-29 18:31:14 UTC 0h
02m 47s ahasenack pass

  trash:// deletion, attributes, restoring for a file in $HOME (API) ... ok
  trash:// deletion, attributes, restoring for a file in $HOME (CLI) ... ok