Closed anon-pradip closed 3 weeks ago
oCIS PR https://github.com/owncloud/ocis/pull/9336 should help the webDavSpecialURLs.feature
test scenarios to pass on reva. The ocis commit id can be bumped again when that oCIS PR has been merged.
Some POSIX FS test scenarios failed unexpectedly. Example: https://drone.owncloud.com/cs3org/reva/4694/34/7
| spaces | "C++ file.cpp" |
Failed step: When user "Alice" uploads file with content "uploaded content" to "C++ file.cpp" using the WebDAV API
TestHelpers\WebDavHelper::getPersonalSpaceIdForUser webdav propfind for user Alice failed with status 404 - so the personal space id cannot be discovered (Exception)
runsh: Total unexpected failed scenarios throughout the test run:
coreApiWebdavUpload/uploadFile.feature:53
I will restart drone CI to see if the test are flaky.
Also there was: https://drone.owncloud.com/cs3org/reva/4694/31/7
Examples:
| ocs-api-version | ocs-status-code |
| 1 | 100 |
Failed step: And uploading content to a public link shared file with password "%public%" should work using the new public WebDAV API
Checking the content of the last public shared file after downloading with the new public WebDAV API
The content was expected to be 'test new', but actually is 'test newata'. HTTP status was 200
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'test new'
+'test newata'
runsh: Total unexpected failed scenarios throughout the test run:
coreApiSharePublicLink1/createPublicLinkShare.feature:88
https://drone.owncloud.com/cs3org/reva/4694/33/7
| new |
Failed step: And these etags should not have changed:
WebDavPropertiesContext::theseEtagsShouldNotHaveChanged
The etag '"169e21c9cdd598d3743b8a83802fe00e"' of element '/upload/file.txt' of user 'Alice' changed to '"a6a2af996d4739063f6ac0a1c4d51d20"'.
Failed asserting that 1 matches expected 0.
runsh: Total unexpected failed scenarios throughout the test run:
coreApiWebdavEtagPropagation2/copyFileFolder.feature:116
drone CI passed this time. So it seems that there are some flaky things with the API tests when the new Posix FS storage driver is used. We need to monitor that to see if it is frequent.
drone CI passed this time. So it seems that there are some flaky things with the API tests when the new Posix FS storage driver is used. We need to monitor that to see if it is frequent.
And can you please tell me how can we monitor that oftenly?
And can you please tell me how can we monitor that oftenly?
I made an issue https://github.com/owncloud/ocis/issues/9340
When we bump the commit id and if unexpected failures happen, we can mention it in the issue.
Part of https://github.com/owncloud/QA/issues/853