[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3369: Allow the ratchet job to pass if tests pass which are not listed as expected to pass

[Tahoe-LAFS]

#3369: Allow the ratchet job to pass if tests pass which are not listed as
expected to pass
---------------------+----------------------------------
 Reporter:  exarkun  |          Owner:
     Type:  defect   |         Status:  new
 Priority:  normal   |      Milestone:  Support Python 3
Component:  unknown  |        Version:  n/a
 Keywords:           |  Launchpad Bug:
---------------------+----------------------------------
 While porting fileutil (ticket:3358) the ratchet job complained that some
 non-fileutil tests started passing.  These tests were incidental to the
 porting effort and they may not _actually_ represent
 successfully/completely ported implementation and tests.  It was a little
 surprising to have to add them to the ratchet-passing list and a little
 confusing to review those additions.  The tests may also flap back to
 failing in other porting effort bumps them in the wrong way.  This would
 create friction for that future porting effort.

 The downside of allowing this is that the CI job won't force porters to
 add the tests they've ported to the list so it will require more care
 during that part of the process.  Of course, if tests are missed then they
 can always be added to the list at a later stage when someone realizes
 they've actually been ported.  This doesn't seem like *that* bad of a
 downside.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3369>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage