Skip to content
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

fileVersion failure in apiMain on master and stable10 #33792

Closed
PVince81 opened this issue Dec 6, 2018 · 6 comments · Fixed by #33795 or #33805
Closed

fileVersion failure in apiMain on master and stable10 #33792

PVince81 opened this issue Dec 6, 2018 · 6 comments · Fixed by #33795 or #33805
Assignees
Labels
p1-urgent Critical issue, need to consider hotfix with just that issue Type:Bug
Milestone

Comments

@PVince81
Copy link
Contributor

PVince81 commented Dec 6, 2018

On master and stable10 I get this error:

  @smokeTest @skipOnStorage:ceph @files_primary_s3-issue-161
  Scenario Outline: Uploading a chunked file does create the correct version that can be restored                    # /srv/www/htdocs/owncloud/tests/acceptance/features/apiMain/fileVersions.feature:66                                                                                                                                                                                 
    Given using <dav-path> DAV path                                                                                  # FeatureContext::usingOldOrNewDavPath()
    When user "user0" uploads file "filesForUpload/davtest.txt" to "/textfile0.txt" in 2 chunks using the WebDAV API # FeatureContext::userUploadsAFileToWithChunks()
    And user "user0" uploads file "filesForUpload/lorem.txt" to "/textfile0.txt" in 3 chunks using the WebDAV API    # FeatureContext::userUploadsAFileToWithChunks()
    Then the version folder of file "/textfile0.txt" for user "user0" should contain "2" elements                    # FilesVersionsContext::theVersionFolderOfFileShouldContainElements()
    When user "user0" restores version index "1" of file "/textfile0.txt" using the WebDAV API                       # FilesVersionsContext::userRestoresVersionIndexOfFile()
    Then the content of file "/textfile0.txt" for user "user0" should be "Dav-Test"                                  # FeatureContext::contentOfFileForUserShouldBe()

    Examples:
      | dav-path |
      | old      |
        Failed asserting that 1 matches expected '2'.

--- Failed scenarios:

    /srv/www/htdocs/owncloud/tests/acceptance/features/apiMain/fileVersions.feature:76

this also happens on the commit that introduced this test from #33743

strange that we didn't noticed this before.

this is blocking stable10/master PR including 10.1 related ones.

once fixed in both master and stable10 please rebase #33302 and #33785

@PVince81
Copy link
Contributor Author

PVince81 commented Dec 6, 2018

Strangely CI reported green for apiMain here https://drone.owncloud.com/owncloud/core/13263/261 for commit 06a1eec. But now when I run the test locally for said commit it fails as well with the above error.

Could this be env related ?

@ownclouders
Copy link
Contributor

GitMate.io thinks possibly related issues are #31155 ([stable10] Backport of languages from master), #32033 ([stable10] Backport of languages from master), #32687 ([stable10] Backport of languages from master), #32557 ([stable10] Backport of languages from master), and #26488 (Fix 7.1.0RC4 test failures on master).

@phil-davis
Copy link
Contributor

PRs #33793 and #33794 demonstrate 50% failure rate

@individual-it
Copy link
Member

reopening because it happened again in https://drone.owncloud.com/owncloud/core/13305

@individual-it individual-it reopened this Dec 7, 2018
@individual-it
Copy link
Member

@phil-davis
Copy link
Contributor

and in the merge commit drone run https://drone.owncloud.com/owncloud/core/13302/255

@PVince81 PVince81 modified the milestones: development, QA Jan 11, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jan 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
p1-urgent Critical issue, need to consider hotfix with just that issue Type:Bug
Projects
None yet
4 participants