https://github.com/jwodder/fuse-devenv

Vagrant setup for testing datalad-fuse
https://github.com/jwodder/fuse-devenv

test vagrant

Last synced: 20 days ago
JSON representation

Vagrant setup for testing datalad-fuse

• Host: GitHub
• URL: https://github.com/jwodder/fuse-devenv
• Owner: jwodder
• License: mit
• Created: 2021-10-08T14:51:10.000Z (about 3 years ago)
• Default Branch: master
• Last Pushed: 2023-10-06T21:08:50.000Z (about 1 year ago)
• Last Synced: 2023-10-06T22:24:51.775Z (about 1 year ago)
• Topics: test, vagrant
• Language: Python
• Homepage:
• Size: 21.5 KB
• Stars: 0
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
This is a [Vagrant](https://www.vagrantup.com) setup for testing out the

`fusefs` command of [`datalad-fuse`](https://github.com/datalad/datalad-fuse).

Create and enter the environment with:

```bash

vagrant up

vagrant ssh

```

Destroy the environment with:

```bash

vagrant destroy

```

Run FUSE tests inside the environment with:

```bash

cd datalad_fuse

tox -- --libfuse

```

As of commit a0bd825, observe that pytest exits abnormally as soon as the FUSE

tests start and that the temp directory for the first FUSE test is still

FUSE-mounted afterwards.

Test out FUSE directly inside the environment with:

```bash

cd datalad_fuse

tox --notest

source .tox/py3/bin/activate

cd ~/fuse-test/highspeed-bids

datalad fusefs ../mount

# As of commit a0bd825, this only works if participants.json was previously

# fetched with the `fsspec-head` command:

cat ../mount/participants.json

# This doesn't work correctly as of commit a0bd825:

ls -l ../mount

fusermount -u ../mount

```