-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Smashbox tests running against master+encryption #15781
Comments
Those share bugs could come from the read-only cache bug fixed in #15721 |
was just merged - @nickvergessen please rebase and fire up the tests again please. @oparoz THX for the hint - let's see ... |
Nop, still failing, but it might be a problem on my (old) mashine, because they seem to fail on master without encryption aswell |
:( |
The tests fail, because the mount point for the shared file ends with a trailing slash. |
Could be a regression due to this addition by myself: #15570 |
Hmmm no, this is not caused by the PR I mentioned. I ran test_shareDir.py and test_shareFile.py in much older versions in git, and I saw that:
@jnfrmarks did test_shareDir.py ever pass before ? @nickvergessen when running the tests don't forget to add I'll bisect the potential regression. |
The fail for the test_shareFile.py appears since 6a59502 (#12006) from @icewind1991 |
I have raised this separately as I was able to reproduce something: #15786 |
I thought I fixed shareDir - it's a test issue - "shareeTwo" was creating the directory and sync'ing the same directory - causing two directories to be created locally. |
@PVince81 yes it works reliable on stable8. |
@nickvergessen Can you retest |
Still fails with
|
@jnfrmarks @nickvergessen @PVince81 can you please digg into this and find out what's going wrong here? THX |
@nickvergessen does this test fail without encryption too ? Is it specific ? It could also be etag propagation issue. |
Let's make it clearer, regression-wise for test_shareFile.py:
So this failing is not related to encryption. |
thx |
Wait, it's still 6a59502 |
WebDAV PUT fails when putting a shared file, so obviously the file didn't change and smashbox says the md5 didn't change either. |
Without Encryption
With Encryption
So the difference is: |
owncloud/smashbox#70 fixes the encryption specific fails of smashbox. New encryption result is then:
|
owncloud/smashbox#72 fixes shareDir.py (without and with encryption) |
We are now back to green without encryption |
so i guess we can close this now - thx @nickvergessen for taking care |
@nickvergessen did you run them always with |
No, I run each test case individually owncloud/smashbox#88 (because I get problems otherwise with the rundir not being empty in the beginning, fixed by owncloud/smashbox#78 ) |
Without Encryption
test_scrapeLogFile.py
✅test_reshareDir.py
✅test_uploadFiles.py
✅test_shareDir.py
: ✅ Fix failing shareDir test that assumed the dir would not exist smashbox#72test_shareFile.py
: ✅ reported at WebDAV PUT on file share fails with 500 #15786, PR at use cross storage move when renaming the part file during webdav put #16159test_shareGroup.py
: ✅ Fix the user and group names in shareGroup.py smashbox#73test_sharePermissions.py
: ✅ Correctly sync (as owner and recipient) and fix the share call smashbox#74With Encryption
test_scrapeLogFile.py
✅test_reshareDir.py
: Login new users to generate their encryption keys smashbox#70test_uploadFiles.py
: Login new users to generate their encryption keys smashbox#70test_shareDir.py
:test_shareFile.py
: reported at WebDAV PUT on file share fails with 500 #15786test_shareGroup.py
: Fix the user and group names in shareGroup.py smashbox#73test_sharePermissions.py
:The text was updated successfully, but these errors were encountered: