support running tests for an installed version without causing allmydata.test.test_runner.BinTahoe.test_the_right_code to fail #1576
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
1 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#1576
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?
The intended way to run tests for an OS package-manager-installed copy of Tahoe-LAFS is
tahoe debug trial
(which uses the installedtahoe
script on the PATH).This fails with the following error:
because that test doesn't know where the code is supposed to be located. It is OK for the test to be skipped in this case.
(https://bugs.launchpad.net/ubuntu/+source/pycryptopp/+bug/811721/comments/18) is an example of such a failure. (Note that the launchpad bug is otherwise unrelated.)
As nejucomo points out on #tahoe-lafs, it's ugly to need to run the tests with the base of the distribution as the current directory. Perhaps there should be an explicit option to tell 'tahoe debug trial' where the code it is supposed to be testing is. (It could request to be rerun with that option if the current directory does not look like it is a Tahoe distribution.)