[tests-only][full-ci] Bump core commit id to the latest upto 2022-05-25

[kiranparajuli589]

Signed-off-by: Kiran Parajuli kiranparajuli589@gmail.com

Description

Update core commit id to the latest up to date 2022-05-25

Related Issue

• Part of [QA] Bump latest commit id [May 23 - Jun 4] QA#742

Motivation and Context

How Has This Been Tested?

• 🤖

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests only (no source changes)

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation ticket raised:

[kiranparajuli589]

failed at cs3ApiTest-ocis https://drone.owncloud.com/owncloud/ocis/12087/35/5

Scenario: Change treesize of personal home and for only one subtree                                                                                      # /var/lib/cs3api-validator/etag-propagation.feature:60
    Given user "admin" has created a folder "a-folder/a-sub-folder-B" in the home directory with the alias "a-sub-folder-B"                                # steps.go:29 -> *ResourcesFeatureContext
    When user "admin" has uploaded a file "a-folder/a-sub-folder/testfile.txt" with content "text" in the home directory with the alias "testfile.txt"     # steps.go:108 -> *ResourcesFeatureContext
    error statting new file
    Then for user "admin" the treesize of the resource with the alias "Admin Home" should be 4                                                             # steps.go:419 -> *ResourcesFeatureContext
    When user "admin" has uploaded a file "a-folder/a-sub-folder-B/testfile2.txt" with content "text" in the home directory with the alias "testfile2.txt" # steps.go:108 -> *ResourcesFeatureContext
    Then for user "admin" the treesize of the resource with the alias "Admin Home" should be 8                                                             # steps.go:419 -> *ResourcesFeatureContext
    And for user "admin" the treesize of the resource with the alias "a-folder" should be 8                                                                # steps.go:419 -> *ResourcesFeatureContext
    And for user "admin" the treesize of the resource with the alias "a-sub-folder" should be 4                                                            # steps.go:419 -> *ResourcesFeatureContext
    And for user "admin" the treesize of the resource with the alias "a-sub-folder-B" should be 4 

build started again to check if it's a hard failure

[kiranparajuli589]

same failure again.

[kiranparajuli589]

https://drone.owncloud.com/owncloud/ocis/12104/55/9
strange, failed while creating users:
test log:

 And these users have been created with default attributes and without skeleton files in the server:
      │ username │
      │ Alice    │
      │ Brian    │
      │ Carol    │
    ✖ failed
      Error: Error: HTTP Request Failed: Failed while creating user, Status: 401 undefined
          at Object.checkStatus (/usr/src/app/src/helpers/httpHelper.js:44:11)
          at /usr/src/app/src/helpers/graphHelper.js:27:33
          at processTicksAndRejections (node:internal/process/task_queues:96:5)
          at async Promise.all (index 0)
          at async /usr/src/app/src/app.js:61:7
          at /srv/app/web/tests/acceptance/stepDefinitions/middlewareContext.js:38:15
          at processTicksAndRejections (internal/process/task_queues.js:95:5)ssssssssssssssssssssssssssssssssssssssssssssssssss

ocis log

{"level":"error","service":"proxy","error":"{\"id\":\"go.micro.client\",\"code\":500,\"detail\":\"service com.owncloud.api.settings: not found\",\"status\":\"Internal Server Error\"}","time":"2022-05-26T04:26:49Z","message":"Could not load roles"}

middleware logs

[error] - 2022-05-26T04:27:33.265Z : Error: HTTP Request Failed: Failed while creating user, Status: 401 undefined
    at Object.checkStatus (/usr/src/app/src/helpers/httpHelper.js:44:11)
    at /usr/src/app/src/helpers/graphHelper.js:27:33
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Promise.all (index 1)
    at async /usr/src/app/src/app.js:61:7

[kiranparajuli589]

@phil-davis only two pipes fail in which every scenario fails on the user creating step as reported in the above comment. do you have any idea about this?

[phil-davis]

@phil-davis only two pipes fail in which every scenario fails on the user creating step as reported in the above comment. do you have any idea about this?

no idea - I guess it is some intermittent problem?

I rebased, force pushed and let it run again - not much else we can do right now.

[phil-davis]

https://drone.owncloud.com/owncloud/ocis/12107/42/6

Feature: sharing

  Background:                                                                            # /srv/app/testrunner/tests/acceptance/features/apiShareManagementBasicToShares/createShareToSharesFolder.feature:4
    Given the administrator has set the default folder for received shares to "Shares"   # OccContext::theAdministratorHasSetTheDefaultFolderForReceivedSharesTo()
    And auto-accept shares has been disabled                                             # FeatureContext::autoAcceptSharesHasBeenDisabled()
    And user "Alice" has been created with default attributes and without skeleton files # FeatureContext::userHasBeenCreatedWithDefaultAttributesAndWithoutSkeletonFiles()
      GraphContext::throwHttpException
      Could not create user Alice
      HTTP status code: 401
      Error code: accessDenied
      Message: Unauthorized (Exception)

The pipeline failed to create users right from the start - maybe there is some existing startup/timing issue that is happening "sometimes"

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information