- 16 Oct, 2020 6 commits
-
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
- 15 Oct, 2020 1 commit
-
-
Kirill Smelkov authored
-
- 14 Oct, 2020 2 commits
-
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
- 13 Oct, 2020 2 commits
-
-
Kirill Smelkov authored
-
Kirill Smelkov authored
ZEO4 can have ._addr as either ("host", port) or "path".
-
- 12 Oct, 2020 4 commits
-
-
Kirill Smelkov authored
-
Kirill Smelkov authored
People don't want to raise up soft defaults nexedi/slapos.package!130 (comment 118373) nexedi/slapos.package!130 (comment 118405)
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
- 11 Oct, 2020 13 commits
-
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
Previously if an assert or something failed in spawned thread, the main thread was usually spinning indefinitely = tests hang. -> Switch all threading places to use sync.WorkGroup and this way if a thread fails, all other threads are canceled and the exception is reported back to wg.wait in main thread.
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
This should cure the situation when on testnodes /tmp/wcfs already exists created without sticky bit.
-
Kirill Smelkov authored
So that multiple users can create things inside.
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
- 09 Oct, 2020 3 commits
-
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
- 08 Oct, 2020 2 commits
-
-
Kirill Smelkov authored
-
Kirill Smelkov authored
tFile registers itself to tDB so that defer(tdb.close) that each test does, automatically close all files before trying to unmount wcfs. However if an error happens inside tFile constructor - before the place where `tdb._files.add(t)` was previously located, tDB.close won't close tFile.f, which will leave opened file on the wcfs -> wcfs unmount will fail with EBUSY, and wcfs will be killed with huge backtrace. If we register tFile early, the problem - even if it happens inside tFile constor - will be handled gracefully: opened file closed and wcfs unmounted clearnly - for example with the following short and easy to understand traceback (1.venv) kirr@deb9:~/src/wendelin.core$ python -m pytest -x wcfs/ ============================================== test session starts ============================================== platform linux2 -- Python 2.7.13, pytest-4.6.11, py-1.9.0, pluggy-0.13.1 rootdir: /home/kirr/src/wendelin.core collected 28 items wcfs/wcfs_test.py ..F =================================================== FAILURES ==================================================== ________________________________________________ test_wcfs_basic ________________________________________________ @func def test_wcfs_basic(): t = tDB(); zf = t.zfile defer(t.close) # >>> lookup non-BigFile -> must be rejected with raises(OSError) as exc: t.wc._stat("head/bigfile/%s" % h(t.nonzfile._p_oid)) assert exc.value.errno == EINVAL # >>> file initially empty > f = t.open(zf) wcfs/wcfs_test.py:1080: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ wcfs/wcfs_test.py:322: in open return tFile(t, zf, at=at) wcfs/wcfs_test.py:477: in __init__ mm.lock(t.fmmap, mm.MLOCK_ONFAULT) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > PyErr_SetFromErrno(OSError) E OSError: [Errno 1] Operation not permitted wcfs/internal/mm.pyx:112: OSError --------------------------------------------- Captured stdout call ---------------------------------------------- M: commit -> @at0 (03db288d33c34955) >>> Change history by file: --------------------------------------------- Captured stderr call ---------------------------------------------- wcfs: 2020/10/08 19:13:12 zodb: FIXME: open file:///tmp/testdb_fs.1HuVZF/1.fs: raw cache is not ready for invalidations -> NoCache forced E1008 19:13:12.030532 3251 wcfs.go:2450] kernel FUSE (API 7.26) does not support explicit data cache invalidation E1008 19:13:12.030780 3251 wcfs.go:2450] -> performance will be AWFUL. E1008 19:13:12.030796 3251 wcfs.go:2450] -> you need kernel which includes git.kernel.org/linus/ad2ba64dd489. E1008 19:13:12.030809 3251 wcfs.go:2450] -> (Linux 5.2+, or nxd-fuse-dkms package installed from navytux.spb.ru/pkg) W: wcfs: kernel FUSE (API 7.26) does not support explicit data cache invalidation W: wcfs: -> performance will be AWFUL. W: wcfs: -> you need kernel which includes git.kernel.org/linus/ad2ba64dd489. W: wcfs: -> (Linux 5.2+, or nxd-fuse-dkms package installed from navytux.spb.ru/pkg) ----------------------------------------------- Captured log call ----------------------------------------------- WARNING ZODB.FileStorage:FileStorage.py:398 Ignoring index for /tmp/testdb_fs.1HuVZF/1.fs ====================================== 1 failed, 2 passed in 2.10 seconds =======================================
-
- 07 Oct, 2020 2 commits
-
-
Kirill Smelkov authored
-
Kirill Smelkov authored
Some wcfs bugs are aonly likely to trigger with GOMAXPROCS=1 (see corresponding tox.ini history), same for 2. Go-fuse also has issues with GOMAXPROCS=1 (https://github.com/hanwen/go-fuse/issues/261) that sometimes manifest themselves as hangs with GOMAXPROCS=`nproc` too.
-
- 06 Oct, 2020 1 commit
-
-
Kirill Smelkov authored
-
- 05 Oct, 2020 1 commit
-
-
Kirill Smelkov authored
- it is more clear to run wcfs tests separate - it was confusing to run wcfs unit tests as part of e.g. test.py/fs1-!wcfs (note the "!wcfs" = "non-wcfs")
-
- 04 Oct, 2020 1 commit
-
-
Kirill Smelkov authored
go.mod is inside wcfs/ and if `go test ./...` is ran outside of it, it autodetects to use GOPATH mode and fails to find imports used by wcfs.
-
- 29 Sep, 2020 2 commits
-
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-