Allow the ratchet job to pass if tests pass which are not listed as expected to pass #3369
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#3369
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
While porting fileutil (/tahoe-lafs/trac-2024-07-25/issues/8008) 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.
Closing in favor of #3372.