tahoe-lafs/trac-2024-07-25

Allow the ratchet job to pass if tests pass which are not listed as expected to pass #3369

New issue

Closed

opened 2020-08-06 13:56:24 +00:00 by exarkun · 1 comment

exarkun commented

2020-08-06 13:56:24 +00:00

Owner

While porting fileutil (/tahoe-lafs/trac-2024-07-25/issues/10451) 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.

While porting fileutil ([/tahoe-lafs/trac-2024-07-25/issues/10451](/tahoe-lafs/trac-2024-07-25/issues/10451)) 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.

tahoe-lafs added the

labels 2020-08-06 13:56:24 +00:00

tahoe-lafs added this to the Support Python 3 milestone 2020-08-06 13:56:24 +00:00

chadwhitacre commented

2020-09-10 12:09:24 +00:00

Author

Owner

Closing in favor of #3372.

Closing in favor of #3372.

tahoe-lafs added the

label 2020-09-10 12:09:24 +00:00

chadwhitacre closed this issue

2020-09-10 12:09:24 +00:00

Sign in to join this conversation.

No labels

LeastAuthority.com automation

cannot reproduce

code-frontend-cli

code-frontend-ftp-sftp

code-frontend-magic-folder

code-frontend-web

code-peerselection

dev-infrastructure

somebody else's problem

was already fixed

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#3369

No description provided.