There are 19 failures in this upload.
| Failure ID | Test case ID | Test class | Test case | Message |
|---|---|---|---|---|
| 7d8bfea3-7664-4096-b2c4-c9d4276b3ca4 | c9a538ed-6d42-4bb9-9ee4-53bc66b212b2 | "before all" hook for "authbase0" | realtime/auth "before all" hook for "authbase0" | Could not set up Test App: "Invalid HTTP request: <!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<HTML><HEAD><META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\n<TITLE>ERROR: The request could not be satisfied</TITLE>\n</HEAD><BODY>\n<H1>502 Bad Gateway ERROR</H1>\n<H2>The request could not be satisfied.</H2>\n<HR noshade size=\"1px\">\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n<PRE>\nGenerated by cloudfront (CloudFront) HTTP3 Server\nRequest ID: 9JFtSF0AMehSoQz4p3U1HUH_n8jAvd1nCWhyvvLKzL0fq3FdfNvJKA==\n</PRE>\n<ADDRESS>\n</ADDRESS>\n</BODY></HTML>; statusCode = 502" |
| f4d81689-a5da-4b22-b46f-07e150fd3e15 | c2789e99-694c-4e31-af17-2bb7c162eaf3 | "before all" hook for "channelinit0_with_web_socket_binary_transport" | realtime/channel "before all" hook for "channelinit0_with_web_socket_binary_transport" | Could not set up Test App: "Invalid HTTP request: <!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<HTML><HEAD><META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\n<TITLE>ERROR: The request could not be satisfied</TITLE>\n</HEAD><BODY>\n<H1>502 Bad Gateway ERROR</H1>\n<H2>The request could not be satisfied.</H2>\n<HR noshade size=\"1px\">\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n<PRE>\nGenerated by cloudfront (CloudFront) HTTP3 Server\nRequest ID: SZeCsrDCb0kmuuq8sznUjvi5fmAnte1NthBVAdNomWJcHo3dtTI6bA==\n</PRE>\n<ADDRESS>\n</ADDRESS>\n</BODY></HTML>; statusCode = 502" |
| d9c8146a-6d3f-4509-ac4f-4c2035e0601d | 39ce747f-d619-4bf8-af25-bfc33ddb8afc | "before all" hook for "connectionPing" | realtime/connection "before all" hook for "connectionPing" | Could not set up Test App: "Invalid HTTP request: <!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<HTML><HEAD><META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\n<TITLE>ERROR: The request could not be satisfied</TITLE>\n</HEAD><BODY>\n<H1>502 Bad Gateway ERROR</H1>\n<H2>The request could not be satisfied.</H2>\n<HR noshade size=\"1px\">\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n<PRE>\nGenerated by cloudfront (CloudFront) HTTP3 Server\nRequest ID: KgKtGMCaAKzLGK1fE1B79tP8zvICaGm8ASn6ZSOmWuSFsdAAUQDHUw==\n</PRE>\n<ADDRESS>\n</ADDRESS>\n</BODY></HTML>; statusCode = 502" |
| 8535858a-8510-46e5-be37-e41c9afeb64a | 39ce747f-d619-4bf8-af25-bfc33ddb8afc | "before all" hook for "connectionPing" | realtime/connection "before all" hook for "connectionPing" | done() called multiple times in hook <realtime/connection "before all" hook for "connectionPing"> of file /home/runner/work/ably-js/ably-js/test/realtime/connection.test.js |
| 0c7b1216-cb90-41b9-8a01-8ebcce020ac8 | b601c486-92ab-42c3-8682-b7eff794caab | publishEcho | realtime/message publishEcho | Received exactly one message on rtNoEcho: expected 2 to equal 1 |
| 258999c7-261f-4980-9b0b-915c58186aaa | a48b8526-fefd-4531-b38b-a5aa81258834 | presenceHistory | realtime/presence presenceHistory | Verify correct number of presence messages found: expected 4 to equal 2 |
| 1a1051dd-6421-46ba-bd7b-f4fe338af55a | a48b8526-fefd-4531-b38b-a5aa81258834 | presenceHistory | realtime/presence presenceHistory | done() called multiple times in test <realtime/presence presenceHistory> of file /home/runner/work/ably-js/ably-js/test/realtime/presence.test.js; in addition, done() received error: RequestError: Timeout awaiting 'request' for 10000ms at ClientRequest.<anonymous> (/home/runner/work/ably-js/ably-js/node_modules/got/dist/source/core/index.js:970:65) at Object.onceWrapper (node:events:634:26) at ClientRequest.emit (node:events:531:35) at ClientRequest.origin.emit (/home/runner/work/ably-js/ably-js/node_modules/@szmarczak/http-timer/dist/source/index.js:43:20) at TLSSocket.socketErrorListener (node:_http_client:500:9) at TLSSocket.emit (node:events:519:28) at emitErrorNT (node:internal/streams/destroy:169:8) at emitErrorCloseNT (node:internal/streams/destroy:128:3) at processTicksAndRejections (node:internal/process/task_queues:82:21) at Timeout.timeoutHandler [as _onTimeout] (/home/runner/work/ably-js/ably-js/node_modules/got/dist/source/core/utils/timed-out.js:36:25) at listOnTimeout (node:internal/timers:583:11) at processTimers (node:internal/timers:519:7) { name: 'TimeoutError', code: 'ETIMEDOUT', timings: [Object], event: 'request' } |
| 1f6540ed-adc1-4b83-8438-8c098c341768 | 85c093c7-0c39-44cb-831d-9f902b82a8a6 | presenceClientIdIsImplicit | realtime/presence presenceClientIdIsImplicit | Timeout of 60000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/home/runner/work/ably-js/ably-js/test/realtime/presence.test.js) |
| 71915bea-c629-44a0-81a6-5611f0fecdb0 | b32eca19-953b-4c3d-8b56-7831b862d97f | presence_enter_inherited_clientid | realtime/presence presence_enter_inherited_clientid | Error response received from server: 502 body was: <Buffer 3c 21 44 4f 43 54 59 50 45 20 48 54 4d 4c 20 50 55 42 4c 49 43 20 22 2d 2f 2f 57 33 43 2f 2f 44 54 44 20 48 54 4d 4c 20 34 2e 30 31 20 54 72 61 6e 73 ... 887 more bytes> |
| 42072721-d001-4a65-a41d-e99b85f10e5f | 07559b82-9760-46d8-8fd8-42324da15047 | channel_resumed_flag | realtime/resume channel_resumed_flag | Check resumed flag is true: expected false to equal true |
| 80db0b42-de25-4df0-93c8-f5f9e6e3a796 | fbab70a1-f82d-4152-86e8-20122601f6e1 | Token generation with explicit timestamp | rest/auth Token generation with explicit timestamp | Error response received from server: 502 body was: <Buffer 3c 21 44 4f 43 54 59 50 45 20 48 54 4d 4c 20 50 55 42 4c 49 43 20 22 2d 2f 2f 57 33 43 2f 2f 44 54 44 20 48 54 4d 4c 20 34 2e 30 31 20 54 72 61 6e 73 ... 887 more bytes> |
| 0ede3ef6-8634-4de5-b0d0-0af889f377e8 | 0f05f3f3-84b7-47d0-be3d-c4f594d7b8fb | Rest embedded JWT with encryption | rest/auth Rest embedded JWT with encryption | Timeout awaiting 'request' for 10000ms |
| 2f61aaed-5f07-4a8b-b913-a4f94883f105 | 9c7cb812-c5d8-4296-98ba-f85518e8acf5 | revokes tokens matching the given specifiers | rest/revokeTokens revokes tokens matching the given specifiers | Timeout of 60000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/home/runner/work/ably-js/ably-js/test/rest/batch.test.js) |
| 107f0eac-6585-4681-9e26-95981db2a76e | f4eebca3-45af-4e61-80d9-ccb0c6667907 | accepts optional issuedBefore and allowReauthMargin parameters | rest/revokeTokens accepts optional issuedBefore and allowReauthMargin parameters | Timeout awaiting 'request' for 10000ms |
| 883e11d4-c582-4962-8711-7af64433aa68 | 90333611-38bc-43b2-9259-007720817f28 | "before all" hook for "Blanket intersection with specified key" | rest/capability "before all" hook for "Blanket intersection with specified key" | Timeout awaiting 'request' for 10000ms |
| 52bae65e-3766-4eca-a0d9-175cd6cc3bca | 12117842-a47e-4270-8944-0f3b3f5a7a7b | Store working fallback | rest/fallbacks Store working fallback | Timeout awaiting 'request' for 3000ms |
| a45593f5-3c1c-44c5-85ab-f0fe0e8644a2 | e174a94b-2ca2-49d0-8427-6a30586ef8a4 | history_simple with binary protocol | rest/history history_simple with binary protocol | Error response received from server: 502 body was: <Buffer 3c 21 44 4f 43 54 59 50 45 20 48 54 4d 4c 20 50 55 42 4c 49 43 20 22 2d 2f 2f 57 33 43 2f 2f 44 54 44 20 48 54 4d 4c 20 34 2e 30 31 20 54 72 61 6e 73 ... 887 more bytes> |
| 993d726f-1bf5-4e92-a72e-f235b8e0048d | b66e4930-4a36-4424-afff-51502d3e9461 | history_simple with text protocol | rest/history history_simple with text protocol | Error response received from server: 502 body was: <Buffer 3c 21 44 4f 43 54 59 50 45 20 48 54 4d 4c 20 50 55 42 4c 49 43 20 22 2d 2f 2f 57 33 43 2f 2f 44 54 44 20 48 54 4d 4c 20 34 2e 30 31 20 54 72 61 6e 73 ... 887 more bytes> |
| 7896f0c7-b37d-4ea0-917d-f556d4a5c95b | 4b146c77-312c-4c4c-9504-b350e6e14be7 | history_multiple with binary protocol | rest/history history_multiple with binary protocol | Error response received from server: 502 body was: <Buffer 3c 21 44 4f 43 54 59 50 45 20 48 54 4d 4c 20 50 55 42 4c 49 43 20 22 2d 2f 2f 57 33 43 2f 2f 44 54 44 20 48 54 4d 4c 20 34 2e 30 31 20 54 72 61 6e 73 ... 887 more bytes> |