Pipeline fails with EVENTHISTORY_STORE=nats-js-kv

[kobergj]

In #9361 I switched the default store type for the eventhistory service to nats-js-kv. This is needed to make the use of the activity feature.

However the pipeline fails because of this. Specifically the gdpr export test is failing every time. Needs investigation if this a code or test problem.

[saw-jan]

Failing gdpr e2e test:

Scenario: User should be able to create and download a GDPR export (attempt 2) # tests/e2e/cucumber/features/user-settings/gdprExport.feature:11
   ✔ Before # tests/e2e/cucumber/environment/index.ts:43
   ✔ Given "Admin" creates following users using API # tests/e2e/cucumber/steps/api.ts:7
       | id    |
       | Alice |
   ✔ And "Alice" logs in # tests/e2e/cucumber/steps/ui/session.ts:45
   ✔ And "Alice" opens the user menu # tests/e2e/cucumber/steps/ui/accountMenu.ts:27
   ✔ And "Alice" requests a new GDPR export # tests/e2e/cucumber/steps/ui/accountMenu.ts:33
   ✖ And "Alice" downloads the GDPR export # tests/e2e/cucumber/steps/ui/accountMenu.ts:42
       page.waitForEvent: Timeout 30000ms exceeded while waiting for event "download"
       =========================== logs ===========================
       waiting for event "download"
       ============================================================
           at Object.downloadGdprExport (/drone/src/webTestRunner/tests/e2e/support/objects/account/actions.ts:70:10)
           at Account.downloadGdprExport (/drone/src/webTestRunner/tests/e2e/support/objects/account/index.ts:28:15)
           at World.<anonymous> (/drone/src/webTestRunner/tests/e2e/cucumber/steps/ui/accountMenu.ts:47:52)
   - And "Alice" logs out # tests/e2e/cucumber/steps/ui/session.ts:58
   ✔ After # tests/e2e/cucumber/environment/index.ts:111

we will have a first look on e2e test side.

[amrita-shrestha]

https://drone.owncloud.com/owncloud/ocis/36273/54/9

[SagarGi]

@S-Panta will investigate into it!

[S-Panta]

On testing locally, this seems to be flaky .
When it fails, using page.reload() make the test passes but waiting for sometime in the same page doesn't pass the test

[saw-jan]

The main problem was because of the server responding with 425 while downloading the GDPR report (UI button action). This happens only during e2e test.

[kobergj]

Mmh. This is not supposed to happen.
You mean the call to the graph/v1.0/users/{userid}/exportPersonalData returns a 425?

[saw-jan]

Mmh. This is not supposed to happen. You mean the call to the graph/v1.0/users/{userid}/exportPersonalData returns a 425?

No, I mean the HEAD request /.personal_data_export.json to download the report file. We have mocked PROPFIND request to generate the necessary UI component. And during the test run it looks like the UI component is ready but the file to download is not ready in the server