tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki

Incorporate fuse tests into buildbot flow #621

New Issue
Closed
opened 2009-02-11 17:04:41 +00:00 by nejucomo · 5 comments
nejucomo commented 2009-02-11 17:04:41 +00:00
Copy Link

The automated fuse tests don't seem to be regularly used and may have bitrotted. From the mailing list, it sounds like the blackmatch fuse interface is most popular, but the fuse tests may not run against it.

This ticket is to fix the fuse tests so that they run against all available fuse interfaces.

The automated fuse tests don't seem to be regularly used and may have bitrotted. From the mailing list, it sounds like the blackmatch fuse interface is most popular, but the fuse tests may not run against it. This ticket is to fix the fuse tests so that they run against all available fuse interfaces.
nejucomo added the
code-frontend
minor
defect
1.3.0
 labels 2009-02-11 17:04:41 +00:00
nejucomo added this to the undecided milestone 2009-02-11 17:04:41 +00:00
nejucomo self-assigned this 2009-02-11 17:04:41 +00:00
nejucomo commented 2009-11-16 04:42:59 +00:00
Author
Copy Link

To read about the existing fuse tests, see http://allmydata.org/trac/tahoe/ticket/255

To read about the existing fuse tests, see <http://allmydata.org/trac/tahoe/ticket/255>
nejucomo commented 2009-11-16 04:54:43 +00:00
Author
Copy Link

Replace the comma in the keywords with a space which is the proper separator.

Replace the comma in the keywords with a space which is the proper separator.
davidsarah commented 2010-01-16 01:03:32 +00:00
Owner
Copy Link

#832 was a duplicate:

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 #831 on improving the fuse testing coverage and correctness.

#832 was a duplicate: > 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 #831 on improving the fuse testing coverage and correctness.
tahoe-lafs changed title from Make automated fuse tests run against blackmatch. to Incorporate fuse tests into buildbot flow 2010-01-16 01:03:32 +00:00
zooko commented 2010-05-08 19:22:14 +00:00
Copy Link

This is actually important! It is the current blocker for making our fuse code into a real supported part of Tahoe-LAFS. Priority="major".

This is actually important! It is the current blocker for making our fuse code into a real supported part of Tahoe-LAFS. Priority="major".
zooko added
major
 and removed
minor
 labels 2010-05-08 19:22:14 +00:00
zooko modified the milestone from undecided to eventually 2010-05-08 19:22:14 +00:00
exarkun commented 2019-07-25 12:48:17 +00:00
Copy Link

All FUSE support has been dropped from the repository (the last pieces seemingly by Zooko in 2011).

All FUSE support has been dropped from the repository (the last pieces seemingly by Zooko in 2011).
exarkun added the
wontfix
 label 2019-07-25 12:48:17 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
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

catch-all for anything that can be fixed by writing code but isn't classified better

  
code-dirnodes

anything involving tahoe directories

  
code-encoding

immutable-file encoding format/layout, cap format, encoding/decoding algorithms

  
code-frontend

general frontend things: new user-facing interfaces, FTP/SFTP servers, FUSE-like interfaces

  
code-frontend-cli

CLI tools

  
code-frontend-ftp-sftp

   
code-frontend-magic-folder

   
code-frontend-web

webapi interfaces, user-facing "WUI" interfaces

  
code-mutable

anything involving mutable files: encoding/decoding, share format

  
code-network

Introducer, locating storage servers, establishing/maintaining connections to them

  
code-nodeadmin

node startup/shutdown, tools to create nodes, logging tools, management/monitoring tools, manhole, disk-space-limiting tools

  
code-peerselection

server selection/sorting algorithm, rebalancing code, allocation policy, swarming-download

  
code-storage

storage-server implementation, share-storage directory layout, client-to-server share transfer protocol

  
contrib

problems with non-core things that live in the source:contrib/ directory

  
critical

   
defect

   
dev-infrastructure

things that help us build Tahoe: buildbot, automated speed/memory/code-coverage tests and results-displayers, IRC channels, mailing lists, this Trac instance

  
documentation

docs items. Also use 'docs' keyword on tickets in more specific components.

  
duplicate

   
enhancement

   
fixed

   
invalid

   
major

   
minor

   
n/a

   
normal

   
operational

things involved in running a tahoe grid, external tools to monitor/maintain a grid (like "nodeadmin" but larger-scale). Was also used for issues with the allmydata.com grid.

  
packaging

setup.py script, library dependencies, binary packages, licensing, installation instructions

  
somebody else's problem

   
supercritical

   
task

   
trivial

   
unknown

Uncategorized. All tickets default to this component until someone updates it.

  
was already fixed

   
website

things about the tahoe-lafs.org website (and sometimes this Trac instance, shared with 'dev-infrastructure')

  
wontfix

   
worksforme
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
Milestone
Clear milestone
No items
No Milestone
eventually
Assignees
Clear assignees
No Assignees
nejucomo
4 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#621
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?