Closed amrita-shrestha closed 1 week ago
Failed builds:
coreApiShareManagementToShares/moveReceivedShare.feature:172
:
coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:236
:
First impressions: shares are not immediately available to the share receivers
But it's strange to see only in that particular test scenario
@saw-jan PR related to this CI build has no changes related to this feature file but still fails. Maybe related to this issue Build: https://drone.owncloud.com/owncloud/ocis/36208/43/5
Scenario: user included in multiple groups, shares a folder with a group # /drone/src/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:236
Given these users have been created with default attributes and without skeleton files: # FeatureContext::theseUsersHaveBeenCreatedWithDefaultAttributesAndWithoutSkeletonFiles()
| username |
| Brian |
And group "grp1" has been created # FeatureContext::groupHasBeenCreated()
And group "grp2" has been created # FeatureContext::groupHasBeenCreated()
And user "Alice" has been added to group "grp1" # FeatureContext::userHasBeenAddedToGroup()
And user "Alice" has been added to group "grp2" # FeatureContext::userHasBeenAddedToGroup()
And user "Brian" has been added to group "grp1" # FeatureContext::userHasBeenAddedToGroup()
And user "Brian" has been added to group "grp2" # FeatureContext::userHasBeenAddedToGroup()
And user "Alice" has created folder "/PARENT" # FeatureContext::userHasCreatedFolder()
When user "Alice" shares folder "/PARENT" with group "grp1" using the sharing API # FeatureContext::userSharesFileWithGroupUsingTheSharingApi()
Then user "Brian" should see the following elements # FeatureContext::userShouldSeeTheElements()
| /Shares/PARENT/ |
/remote.php/webdav/Shares/PARENT/ is not in propfind answer but should be
Reproducible on a low-spec machine
@saw-jan PR related to this CI build has no changes related to this feature file but still fails. Maybe related to this issue Build: https://drone.owncloud.com/owncloud/ocis/36208/43/5
yes, the test failure is related to this and I have already added in the list above https://github.com/owncloud/ocis/issues/9428#issuecomment-2182409013
First impressions: shares are not immediately available to the share receivers
But it's strange to see only in that particular test scenario
Can confirm that the shares weren't there while doing MOVE request.
Scenarios that can be flaky due to the same reason:
apiSpacesDavOperation/copyByFileId.feature:208
apiSharingNg/enableDisableShareSync.feature:151
Describe the bug
Flaky tests https://drone.owncloud.com/owncloud/ocis/36078/42/6