Test multiple filesystems with Vagrant#1359
Test multiple filesystems with Vagrant#1359PlasmaPower wants to merge 1 commit intoborgbackup:masterfrom
Conversation
0b43240 to
c6db6e5
Compare
|
Okay, first network based FS is implemented (SSHFS). Implementation is a bit hacky (e.g. rootTestingDir hardcoded in sshd_config, couldn't get ChrootDirectory working), but I've made sure to comment it well and it should work fine as-is. |
|
|
c6db6e5 to
9f81903
Compare
|
Okay, CIFS is done after a lot of trouble with configuration. That means all the filesystems I was planning to test (except NFS which I couldn't) are done! Any more recommendations? I'm now going to test if borg actually succeeds in these filesystems (I'm expecting they'll be bugs :/). |
9ed8620 to
f57427c
Compare
f57427c to
302f1ce
Compare
302f1ce to
ca38a06
Compare
|
Okay, I've added all the drivers I could find to the Vagrantfile, but I might have missed some and some might not exist that I thought existed (or had different names). I'm going to wait on the FS specific issues to be fixed before moving forward though, wouldn't want to have to redo everything. |
vagrant-tools/run-tests.sh
Outdated
| fi | ||
| # otherwise: just use the system python | ||
|
|
||
| testingPartitionSize=128M |
There was a problem hiding this comment.
what is the minimum that would safely work?
There was a problem hiding this comment.
I don't know, and I would like to support future tests. The FS minimum size is usually small, around 10M, so I don't think that's a big problem. Maybe we should drop this to 16M? I'll check that
There was a problem hiding this comment.
Looks like 16M works. Switching to that now.
There was a problem hiding this comment.
16M fails on NTFS, switching to 32M.
There was a problem hiding this comment.
I've switched it back to 16M with a custom value of 128M for NTFS because it still runs out at 32M.
a9d06de to
f02d87d
Compare
|
I think I'm setting some naming conventions here, @ThomasWaldmann do you agree with them? I can change them of course. |
| map to guest = Bad User | ||
|
|
||
| # Who thought it was a good idea | ||
| # to put printing in a file sharing protocol? |
f02d87d to
e4ce1f3
Compare
|
names should be like in pep8. |
|
@ThomasWaldmann Should the names of files/directories also be snake_case? I'm currently using dashes as delimiters, but I can easily switch. |
|
dashes in file/dirnames are fine imho. |
|
That seems like it'll eliminate a number of problems, and enable more tests. I'll switch all the provision commands over to privileged in the Vagrantfile, remove the |
c55dba5 to
ac7afa9
Compare
|
I'm getting really odd errors on CIFS. I've put the debugging info in this gist because it's a bit long. |
|
I'd appreciate help debugging that error. I'm not really sure what's causing it. |
|
Well, seems like a crash in pytest itself. |
|
It does, but I find it odd that it occurs right after a failure in one of our tests. Maybe I should just disable CIFS? |
|
I can't figure this issue out, so for now at least I'm just disabling CIFS. We already are testing a network based FS anyway. |
|
Pity. Maybe we can enable it again later, CIFS is quite popular, even for internet storage boxes. |
|
Yeah, in my local changeset (will push after testing FreeBSD) it's just continued past with a comment explaining the problem. Hopefully that means it'll be easy to re-enable if the problem gets fixed. Also, I'm getting some errors on FreeBSD, issue will be up with detailed information soon. |
90e0af6 to
b8ba248
Compare
|
Okay, I'm going to revisit the PR to rerun tests now that some of them should have been fixed. |
b8ba248 to
21e6384
Compare
Current coverage is 85.43% (diff: 100%)@@ master #1359 diff @@
==========================================
Files 19 19
Lines 6125 6125
Methods 0 0
Messages 0 0
Branches 1033 1033
==========================================
+ Hits 5230 5233 +3
+ Misses 645 643 -2
+ Partials 250 249 -1
|
|
I've been really busy, but I currently have some time to work on this (and I should be relatively free for a while). I'm running tests for wheezy32 now, I'll post logs if anything comes up of course. It's unfortunate that the whole thing has to be rebuilt and dependencies have to be reinstalled for each filesystem. Is there a workaround that I could use? |
|
@PlasmaPower not sure what you mean with rebuilt/reinstalled for each filesystem. but as a general remark: we'll soon have 1.1.0b3 and likely that will be the last beta, follow by 1+ release candidate. so it would be good to get your PR finished soon, so it can be in 1.1.0 release. |
|
another thing: I'ld like to keep the count of toplevel items in the repo low, so how about moving the stuff from vagrant-tools/... to scripts/vagrant/... ? |
|
If anyone else wants to pick up this PR (and claim the bounty), that's fine. The test time is simply too long to try to fix a lot of small issues. Each time tox is run with a different TMPDIR it seems to reinstall dependencies, I haven't looked into preventing this, a symlink in the TMPDIR to a central location might fix it. |
|
And yes, tests are failing on various filesystems, but a lot of the time it's hard to tell where the problem is coming from and if it's the actual tests or just my test driver. Also, it seems to also be somewhat OS dependent. |
|
continued in #1820. |
|
Great! I've followed that issue, I'll be happy to help if you're wondering why something's there/what is does. |
Fixes #1289
Both kernel module and FUSE filesystems are supported.
TODO: