cleanups to backupdb tests #1777
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
3 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#1777
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?
This cleanup patch removes complexity in the backupdb tests that was caused by needing to handle the case where pysqlite is not available. We now depend on Python 2.5 which includes pysqlite in the standard lib.
Attachment no-tests-of-backup-without-sqlite.darcs.patch (110496 bytes) added
I intend to attach more patches as I generate them.
Reviewed. Please check it applies/tests cleanly and land it for 1.10.
The description of this ticket was really vague and not specific to the attached patch. One ticket per batch of closely related cleanups, please!
cleanups to tests and mutables for 1.10to cleanups to backupdb testsNeeds rerecording in git.
I'll land this.
An equivalent change was already made in changeset:a1a1b5bf8a6e1a09.
That commit, although made before 1.9.2 was released, was not in the 1.9.2 branch (which is unsurprising since it is a cleanup and 1.9.2 was a point release), so 1.10 will be the first release to have it.