[tests-only] Tag recursive copy scenario with issue number#40212
Merged
phil-davis merged 2 commits intomasterfrom Jul 16, 2022
Merged
[tests-only] Tag recursive copy scenario with issue number#40212phil-davis merged 2 commits intomasterfrom
phil-davis merged 2 commits intomasterfrom
Conversation
a3fef09 to
82312cc
Compare
|
Kudos, SonarCloud Quality Gate passed! |
Contributor
Author
|
@SagarGi can you give a "green tick" approval please, so that I can merge this PR. |
SagarGi
approved these changes
Jul 16, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.








Description
The new test scenario "Copying a folder into a sub-folder of itself" has similar recursive problem to the scenario "Moving a folder into a sub-folder of itself". There was a problem in reva-oCIS with this sending the server into an infinite recursion.
The problem has been fixed in reva edge branch, and in oCIS. But the inifinite recursion still happens in reva master branch. reva master branch CI has a filter for
~@issue-ocis-3023- to avoid running the scenario(s) that have this problem.This PR tags the new scenario so that it will not be run in reva master.
The problem was noticed when bumping the core commit id in cs3org/reva#3076 (comment)
2nd commit: bump sabre dependencies (just because patch bumps are available - not related to the skipping)
How Has This Been Tested?
CI
Types of changes
Checklist: