Incorporate fuse tests into buildbot flow. #832

Closed
opened 2009-11-16 05:20:11 +00:00 by nejucomo · 1 comment

The fuse interfaces have a history of bitrotting. This would be alleviated if we incorporated the tests into the buildbot flow.

Because they live in /contrib and they depend on packages outside of the official Tahoe-LAFS dependencies and they may confuse the kernel or filesystem, it might make sense to have a separate buildbot process for /contrib or fuse interfaces.

See also this ticket on improving the fuse testing coverage and correctness:

http://allmydata.org/trac/tahoe/ticket/831

The fuse interfaces have a history of bitrotting. This would be alleviated if we incorporated the tests into the buildbot flow. Because they live in /contrib and they depend on packages outside of the official Tahoe-LAFS dependencies and they may confuse the kernel or filesystem, it might make sense to have a separate buildbot process for /contrib or fuse interfaces. See also this ticket on improving the fuse testing coverage and correctness: <http://allmydata.org/trac/tahoe/ticket/831>
nejucomo added the
contrib
major
enhancement
1.5.0
labels 2009-11-16 05:20:11 +00:00
nejucomo added this to the undecided milestone 2009-11-16 05:20:11 +00:00
davidsarah commented 2010-01-16 01:00:52 +00:00
Owner

Duplicate of #621.

Duplicate of #621.
tahoe-lafs added the
duplicate
label 2010-01-16 01:00:52 +00:00
davidsarah closed this issue 2010-01-16 01:00:52 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#832
No description provided.