Skip to content

MatrixClient.setAccountData: await remote echo. #11076

MatrixClient.setAccountData: await remote echo.

MatrixClient.setAccountData: await remote echo. #11076

Triggered via pull request February 7, 2025 16:51
Status Failure
Total duration 1m 47s
Artifacts

tests.yml

on: pull_request
Matrix: Downstream test element-web / Jest
Waiting for pending jobs
Matrix: jest
Run Complement Crypto tests  /  tests
Run Complement Crypto tests / tests
Downstream test element-web  /  jest-tests
Downstream test element-web / jest-tests
Jest tests
0s
Jest tests
Downstream Complement Crypto tests
0s
Downstream Complement Crypto tests
Downstream tests
1s
Downstream tests
Fit to window
Zoom out
Zoom in

Annotations

26 errors
MatrixClient › delete account data › makes correct request when deletion is not supported by server: src/client.ts#L2267
TypeError: Cannot read properties of undefined (reading 'get') at get (src/client.ts:2267:71) at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:17) at _next (node_modules/@babel/runtime/helpers/asyncToGenerator.js:17:9) at node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:7 at node_modules/@babel/runtime/helpers/asyncToGenerator.js:14:12 at MatrixClient.deleteAccountData (src/client.ts:2281:98) at Object.deleteAccountData (spec/unit/matrix-client.spec.ts:2865:36) at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:17) at _next (node_modules/@babel/runtime/helpers/asyncToGenerator.js:17:9)
parseErrorResponse › should handle no type gracefully: spec/unit/http-api/utils.spec.ts#L268
expect(received).toStrictEqual(expected) // deep equality Expected: [Error: Server returned 500 error] Received: [Error: Server returned 500 error for undefined] at Object.toStrictEqual (spec/unit/http-api/utils.spec.ts:268:11)
Jest [unit] (Node 22)
Process completed with exit code 1.
Jest [unit] (Node lts/*)
The job was canceled because "unit_22" failed.
MatrixClient › delete account data › makes correct request when deletion is not supported by server: src/client.ts#L2267
TypeError: Cannot read properties of undefined (reading 'get') at get (src/client.ts:2267:71) at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:17) at _next (node_modules/@babel/runtime/helpers/asyncToGenerator.js:17:9) at node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:7 at node_modules/@babel/runtime/helpers/asyncToGenerator.js:14:12 at MatrixClient.deleteAccountData (src/client.ts:2281:98) at Object.deleteAccountData (spec/unit/matrix-client.spec.ts:2865:36) at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:17) at _next (node_modules/@babel/runtime/helpers/asyncToGenerator.js:17:9)
parseErrorResponse › should handle no type gracefully: spec/unit/http-api/utils.spec.ts#L268
expect(received).toStrictEqual(expected) // deep equality Expected: [Error: Server returned 500 error] Received: [Error: Server returned 500 error for undefined] at Object.toStrictEqual (spec/unit/http-api/utils.spec.ts:268:11)
Jest [unit] (Node lts/*)
The operation was canceled.
Jest [integ] (Node lts/*)
The job was canceled because "unit_22" failed.
Device dehydration › should rehydrate and dehydrate a device: src/client.ts#L2168
Cannot `setAccountData` before the client is started: try `setAccountDataRaw` at src/client.ts:2168:19 at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:17) at _next (node_modules/@babel/runtime/helpers/asyncToGenerator.js:17:9) at node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:7 at node_modules/@babel/runtime/helpers/asyncToGenerator.js:14:12 at MatrixClient.setAccountData (src/client.ts:2202:10) at setAccountData (src/secret-storage.ts:447:39) at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:17) at _next (node_modules/@babel/runtime/helpers/asyncToGenerator.js:17:9)
cross-signing › bootstrapCrossSigning (before initialsync completes) › will upload existing cross-signing keys to an established secret storage: src/client.ts#L2168
Cannot `setAccountData` before the client is started: try `setAccountDataRaw` at src/client.ts:2168:19 at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:17) at _next (node_modules/@babel/runtime/helpers/asyncToGenerator.js:17:9) at node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:7 at node_modules/@babel/runtime/helpers/asyncToGenerator.js:14:12 at MatrixClient.setAccountData (src/client.ts:2202:10) at setAccountData (src/secret-storage.ts:553:39) at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:17) at _next (node_modules/@babel/runtime/helpers/asyncToGenerator.js:17:9)
crypto › Secret Storage and Key Backup › bootstrapSecretStorage › should upload cross signing keys: spec/integ/crypto/crypto.spec.ts#L1998
thrown: "Exceeded timeout of 5000 ms for a test. Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout." at it (spec/integ/crypto/crypto.spec.ts:1998:13) at describe (spec/integ/crypto/crypto.spec.ts:1902:9) at describe (spec/integ/crypto/crypto.spec.ts:1749:5) at Object.describe (spec/integ/crypto/crypto.spec.ts:209:1)
crypto › Secret Storage and Key Backup › bootstrapSecretStorage › should create a new megolm backup: spec/integ/crypto/crypto.spec.ts#L2031
thrown: "Exceeded timeout of 5000 ms for a test. Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout." at it (spec/integ/crypto/crypto.spec.ts:2031:13) at describe (spec/integ/crypto/crypto.spec.ts:1902:9) at describe (spec/integ/crypto/crypto.spec.ts:1749:5) at Object.describe (spec/integ/crypto/crypto.spec.ts:209:1)
crypto › Secret Storage and Key Backup › bootstrapSecretStorage › should upload existing megolm backup key to a new 4S store: spec/integ/crypto/crypto.spec.ts#L2050
thrown: "Exceeded timeout of 5000 ms for a test. Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout." at it (spec/integ/crypto/crypto.spec.ts:2050:13) at describe (spec/integ/crypto/crypto.spec.ts:1902:9) at describe (spec/integ/crypto/crypto.spec.ts:1749:5) at Object.describe (spec/integ/crypto/crypto.spec.ts:209:1)
crypto › Secret Storage and Key Backup › Manage Key Backup › Should be able to restore from 4S after bootstrap: spec/integ/crypto/crypto.spec.ts#L2083
thrown: "Exceeded timeout of 5000 ms for a test. Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout." at it (spec/integ/crypto/crypto.spec.ts:2083:13) at describe (spec/integ/crypto/crypto.spec.ts:2077:9) at describe (spec/integ/crypto/crypto.spec.ts:1749:5) at Object.describe (spec/integ/crypto/crypto.spec.ts:209:1)
crypto › Secret Storage and Key Backup › Manage Key Backup › Reset key backup should create a new backup and update 4S: spec/integ/crypto/crypto.spec.ts#L2131
thrown: "Exceeded timeout of 5000 ms for a test. Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout." at it (spec/integ/crypto/crypto.spec.ts:2131:13) at describe (spec/integ/crypto/crypto.spec.ts:2077:9) at describe (spec/integ/crypto/crypto.spec.ts:1749:5) at Object.describe (spec/integ/crypto/crypto.spec.ts:209:1)
Jest [integ] (Node lts/*)
The operation was canceled.
Jest [integ] (Node 22)
The job was canceled because "unit_22" failed.
Device dehydration › should rehydrate and dehydrate a device: src/client.ts#L2168
Cannot `setAccountData` before the client is started: try `setAccountDataRaw` at src/client.ts:2168:19 at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:17) at _next (node_modules/@babel/runtime/helpers/asyncToGenerator.js:17:9) at node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:7 at node_modules/@babel/runtime/helpers/asyncToGenerator.js:14:12 at MatrixClient.setAccountData (src/client.ts:2202:10) at setAccountData (src/secret-storage.ts:447:39) at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:17) at _next (node_modules/@babel/runtime/helpers/asyncToGenerator.js:17:9)
cross-signing › bootstrapCrossSigning (before initialsync completes) › will upload existing cross-signing keys to an established secret storage: src/client.ts#L2168
Cannot `setAccountData` before the client is started: try `setAccountDataRaw` at src/client.ts:2168:19 at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:17) at _next (node_modules/@babel/runtime/helpers/asyncToGenerator.js:17:9) at node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:7 at node_modules/@babel/runtime/helpers/asyncToGenerator.js:14:12 at MatrixClient.setAccountData (src/client.ts:2202:10) at setAccountData (src/secret-storage.ts:553:39) at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:17) at _next (node_modules/@babel/runtime/helpers/asyncToGenerator.js:17:9)
crypto › Secret Storage and Key Backup › bootstrapSecretStorage › should upload cross signing keys: spec/integ/crypto/crypto.spec.ts#L1998
thrown: "Exceeded timeout of 5000 ms for a test. Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout." at it (spec/integ/crypto/crypto.spec.ts:1998:13) at describe (spec/integ/crypto/crypto.spec.ts:1902:9) at describe (spec/integ/crypto/crypto.spec.ts:1749:5) at Object.describe (spec/integ/crypto/crypto.spec.ts:209:1)
crypto › Secret Storage and Key Backup › bootstrapSecretStorage › should create a new megolm backup: spec/integ/crypto/crypto.spec.ts#L2031
thrown: "Exceeded timeout of 5000 ms for a test. Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout." at it (spec/integ/crypto/crypto.spec.ts:2031:13) at describe (spec/integ/crypto/crypto.spec.ts:1902:9) at describe (spec/integ/crypto/crypto.spec.ts:1749:5) at Object.describe (spec/integ/crypto/crypto.spec.ts:209:1)
crypto › Secret Storage and Key Backup › bootstrapSecretStorage › should upload existing megolm backup key to a new 4S store: spec/integ/crypto/crypto.spec.ts#L2050
thrown: "Exceeded timeout of 5000 ms for a test. Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout." at it (spec/integ/crypto/crypto.spec.ts:2050:13) at describe (spec/integ/crypto/crypto.spec.ts:1902:9) at describe (spec/integ/crypto/crypto.spec.ts:1749:5) at Object.describe (spec/integ/crypto/crypto.spec.ts:209:1)
crypto › Secret Storage and Key Backup › Manage Key Backup › Should be able to restore from 4S after bootstrap: spec/integ/crypto/crypto.spec.ts#L2083
thrown: "Exceeded timeout of 5000 ms for a test. Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout." at it (spec/integ/crypto/crypto.spec.ts:2083:13) at describe (spec/integ/crypto/crypto.spec.ts:2077:9) at describe (spec/integ/crypto/crypto.spec.ts:1749:5) at Object.describe (spec/integ/crypto/crypto.spec.ts:209:1)
crypto › Secret Storage and Key Backup › Manage Key Backup › Reset key backup should create a new backup and update 4S: spec/integ/crypto/crypto.spec.ts#L2131
thrown: "Exceeded timeout of 5000 ms for a test. Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout." at it (spec/integ/crypto/crypto.spec.ts:2131:13) at describe (spec/integ/crypto/crypto.spec.ts:2077:9) at describe (spec/integ/crypto/crypto.spec.ts:1749:5) at Object.describe (spec/integ/crypto/crypto.spec.ts:209:1)
Jest [integ] (Node 22)
The operation was canceled.
Jest tests
Process completed with exit code 1.