aboutsummaryrefslogtreecommitdiff
path: root/test/test_examples.py
Commit message (Collapse)AuthorAge
* Don't assume sub-second resolution for st_atime/st_mtime.Gravatar Nikolaus Rath2018-07-11
| | | | Fixes: #224
* example/ioctl: build on FreeBSD, but add protocol check instead.Gravatar Nikolaus Rath2017-08-25
|
* examples/{ioctl,null}: don't build under FreeBSD instead of skipping tests.Gravatar Nikolaus Rath2017-08-25
|
* Skip testing null and ioctl examples under FreeBSD.Gravatar Nikolaus Rath2017-08-24
| | | | | This seems to be unsupported. However, me may also be doing it wrong. I've asked on the freebsd-fs list for help.
* Removed unused import.Gravatar Nikolaus Rath2017-08-24
|
* Use printcap() to control test executionGravatar Nikolaus Rath2017-08-24
| | | | That way, we run only tests that are supported by the running kernel.
* Added testcase for examples/printcapGravatar Nikolaus Rath2017-08-24
|
* Skip tests that aren't supported under FreeBSD.Gravatar Nikolaus Rath2017-08-11
|
* Don't build passthrough_ll under BSD.Gravatar Nikolaus Rath2017-08-11
|
* os_open(): don't attempt to close fd if open failed.Gravatar Nikolaus Rath2017-08-06
|
* Added writeback cache to passthrough_llGravatar Nikolaus Rath2017-08-06
| | | | | | | | This fixes issue #191 (where the test was done by simply adding FUSE_CAP_WRITEBACK_CACHE without adjusting the flags in the open() call). Fixes: #191.
* Added append and seek testsGravatar Nikolaus Rath2017-08-04
|
* Don't check st_nlink value for mkdirGravatar Nikolaus Rath2017-08-03
| | | | | | Some filesystems don't track this for directories. Fixes: #180.
* tst_readdir(): actually go through FUSEGravatar Nikolaus Rath2017-06-20
| | | | The previous code didn't actually go through the mountpoint at all.
* examples/passthrough_ll: added support for create()Gravatar Nikolaus Rath2017-06-05
|
* example/passthrough_ll: added write supportGravatar Nikolaus Rath2017-06-05
|
* tst_link(): wait for RELEASE requestGravatar Nikolaus Rath2017-05-31
| | | | | | | | | | Since RELEASE requests are asynchronous, it is possible that libfuse still considers the file to be open when userspace has closed it, so that a successive unlink() call from userspace actually triggers a rename(). We avoid the resulting test failure by re-trying a few times. Fixes: #157.
* Factored out C-based testsGravatar Nikolaus Rath2017-05-25
|
* tst_link(): add more assertionsGravatar Nikolaus Rath2017-05-25
| | | | Hopefully this helps debugging issue #157.
* Added tst_open_read()Gravatar Nikolaus Rath2017-05-24
| | | | | Slightly increases coverage of examples/passthrough_ll.c (which supports open for reading, but not for writing).
* Actually test passthrough* examplesGravatar Nikolaus Rath2017-04-07
| | | | | | | | Since os.path.join() interprets leading slashes, we were actually never accessing the mountpoint and doing all the tests in the source directory. Fixes: #139
* test_examples(): test without debug messages firstGravatar Nikolaus Rath2017-04-07
| | | | | That way, we are not drowning in messages when a test would also fail without debugging enabled.
* test_examples(): avoid false positives from fuse debug outputGravatar Nikolaus Rath2017-04-07
|
* passthrough_ll: only test functions that are actually providedGravatar Nikolaus Rath2017-04-07
| | | | | | This appeared to work because of an unrelated bug that caused us to actually never access the mountpoint at all and do all tests on the lower filesystem. This issue will be fixed in a separate commit.
* Remove checked_unlink()Gravatar Nikolaus Rath2017-04-07
| | | | | There is no reason why so many tests require the file system to support unlink() and/or rmdir().
* Turn tst_mknod() into tst_create()Gravatar Nikolaus Rath2017-04-07
| | | | | Ensure that we are really creating a new file. Don't attempt to write, we do that in tst_open_write().
* Renamed tst_write() to tst_open_write()Gravatar Nikolaus Rath2017-04-07
| | | | | We are actually testing both opening of an existing file and writing to it.
* Added tst_unlink()Gravatar Nikolaus Rath2017-04-07
| | | | To check for unlink() support without requiring create()/mknod().
* tst_mkdir(): factor out tst_rmdir()Gravatar Nikolaus Rath2017-04-07
| | | | | This allows testing a filesystem that offers mkdir(), but no rmdir() (and vice versa).
* Rename tst_unlink() to tst_open_unlink()Gravatar Nikolaus Rath2017-04-07
| | | | | This makes more sense, since we are specifically checking unlinking of an open file.
* tst_readdir(): don't require create/mkdir supportGravatar Nikolaus Rath2017-04-07
| | | | | | By creating the files in the lower filesystem, we can test readdir() even for filesystems that don't implement create() or mkdir().
* Added experimental support for building with Meson+NinjaGravatar Nikolaus Rath2017-01-12
|
* Skip tests if not root and no setuid fusermount3.Gravatar Nikolaus Rath2017-01-10
|
* Added documentation and test case for null exampleGravatar Nikolaus Rath2016-12-23
|
* Fix segfault in debug logging codeGravatar Nikolaus Rath2016-10-24
| | | | fi may be NULL, so we need to protect against this.
* fuse_new(): don't accept options that don't make sense for end-usersGravatar Nikolaus Rath2016-10-20
| | | | | | Several options (use_ino, etc) depend on the file system implementation. Allowing them to be set from the command line makes no sense.
* Unify handling of fuse_conn_info optionsGravatar Nikolaus Rath2016-10-15
| | | | | | Instead of using command line options to modify struct fuse_conn_info before and after calling the init() handler, we now give the file system explicit control over this.
* tests: use freshly-build fusermount (instead of system version)Gravatar Nikolaus Rath2016-10-13
| | | | When running tests as non-root, make fusermount setuid root.
* Only test writeback cache if kernel is recent enough.Gravatar Nikolaus Rath2016-10-13
|
* Fix race condition in notify_* examplesGravatar Nikolaus Rath2016-10-10
| | | | | | | The fix in commit cf4159156b was incomplete. While some false positives are caused by sleep() in the file system taking longer than expected, there was also a race condition where the file system would run before the contents are initialized properly.
* Added write cache tests.Gravatar Nikolaus Rath2016-10-10
|
* Added cuse unit test.Gravatar Nikolaus Rath2016-10-09
|
* Increase timeouts in notify_* testsGravatar Nikolaus Rath2016-10-09
| | | | When running under Valgrind, we otherwise get sporadic test failures.
* Renamed timefsN examples to fuse_notify_*Gravatar Nikolaus Rath2016-10-09
| | | | | This should make it more obvious at first glance what the different examples do.
* Renamed ioctl and poll examplesGravatar Nikolaus Rath2016-10-09
| | | | | The new names should make it more obvious at first glance what each example demonstrates.
* Renamed some examples to make their function more obviousGravatar Nikolaus Rath2016-10-09
| | | | Also, added more comments for the same purpose.
* Added timefs3 to test notify_inval_entry.Gravatar Nikolaus Rath2016-10-08
| | | | Fixes #32.
* Added timefs[12] examples.Gravatar Nikolaus Rath2016-10-08
| | | | | These examplesdemonstrate the use of the `fuse_lowlevel_notify_store` and `fuse_lowlevel_notify_inval_inode` functions.
* Removed ``-o big_writes`` optionGravatar Nikolaus Rath2016-10-08
| | | | | | This option is obsolete and should always be enabled. File systems that want to limit the size of write requests should use the ``-o max_write=<N>`` option instead.
* Test more combinations of low-level options.Gravatar Nikolaus Rath2016-10-05
|