BuildBot step to run tests from package #348
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#348
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
Patches that change packaging can't be conveniently tested by trial tests inside the package. A better way to test such things is to have a BuildStep which, after a package has been built (such as a source tarball or a py2exe or py2app package), it installs that package and then runs the unit tests from the version thus installed.
This would help test patches like #335 (OSError when trying to access !http://localhost:8123/provisioning/), it would catch errors in the build process which cause packages to be built incorrectly (such as the one that distracted several of us from more useful labor Monday morning), and if implemented in re-usable BuildBot code, it would help test similar issues in other projects such as Nevow #2527, Nevow #857, pyflakes #2535, and twisted #2308.
I added a ticket on buildbot #199 for this.
I updated buildbot #199 to suggest installing into a local, newly created subdirectory and testing that install by setting the PYTHONPATH to point to that subdirectory.
Nevow #2630 (installation of Nevow doesn't have automated tests) has been fixed -- the Nevow buildbot now tests installation of Nevow. We could do similarly for Tahoe.
See also #434 (automate testing of installation) which is perhaps going to be fixed by the same patch that fixes this ticket -- if that patch makes it so that the buildbot both installs the package and runs the unit tests from the installed package.
Chris has done this!