Details of upload cd60a910-8d89-4f1d-b695-57c1d5f8e1de

Created at
2026-03-06T14:15:32.739Z
Total number of tests
1127
JUnit report XML
View report
GitHub repository
ably/ably-js
Commit SHA
a2b8b23
Pull request base ref
integration/protocol-v6
Pull request head ref
PUB-1197/liveobjects-rest-api
Branch / tag name
2109/merge
Workflow asset retention period
90 days
GitHub action
__ably_test-observability-action
GitHub run ID
22766594271
GitHub run attempt
1
GitHub run number
4052
GitHub job
test-node
GitHub job URL
Not known
Loop iteration
1

Test failures

There are 9 failures in this upload.

Failure ID Test case ID Test class Test case Message
915e2d09-34c3-46a0-b7c9-fb7334844f7d 6dd53a75-13fc-433b-adbe-7d2237761f23 attachWithChannelModes with web_socket binary protocol realtime/channel attachWithChannelModes with web_socket binary protocol done() invoked with non-Error: checkCanPresenceSubscribe: message not received within 5s
65cf7312-29a2-453a-b911-32160c1900e2 5b7a69d0-a7b9-426b-b0b9-42f0d49d59e7 should handle complex object operations workflow with binary protocol rest/objects Rest with Objects plugin should handle complex object operations workflow with binary protocol expected { complexMap: { …(5) }, …(1) } to have deep property 'counter' of 11, but got { Object (objectId) }
eddf503f-c89e-4214-a247-a3d78aeca316 f78fc8dd-b679-4f7c-a551-aaa6a0734863 should handle complex object operations workflow with text protocol rest/objects Rest with Objects plugin should handle complex object operations workflow with text protocol expected { …(2) } to have deep property 'counter' of 11, but got { Object (objectId) }
e4993f88-0b47-4863-a2a1-791fdb306b5d f3eaa472-3a97-4301-9bdd-4d8808446097 should handle different data types for expanded objects with binary protocol rest/objects Rest with Objects plugin RestObject.get() should handle different data types for expanded objects with binary protocol Check data for key "emptyBytesKey" is retrieved correctly in expanded object: expected false to be true
b4c58f35-f092-4594-8690-05b15b031dc1 eb789cb3-f4d1-4484-b9ec-d193bcddc895 should handle different data types for expanded objects with text protocol rest/objects Rest with Objects plugin RestObject.get() should handle different data types for expanded objects with text protocol Check data for key "emptyBytesKey" is retrieved correctly in expanded object: expected false to be true
6e6491e4-11c6-44a5-95e6-c8a1aa6a442a 83b908cb-ceac-4948-b89b-89a247797f56 should handle different data types in MAP_SET operation with binary protocol rest/objects Rest with Objects plugin RestObject.publish() should handle different data types in MAP_SET operation with binary protocol Check data was set for a key "emptyBytesKey" via MAP_SET: expected false to be true
c01d9468-eea8-4711-8b2d-ba708d968283 9ee9655a-6289-4930-bc3f-54f3f7dccab1 should handle different data types in MAP_SET operation with text protocol rest/objects Rest with Objects plugin RestObject.publish() should handle different data types in MAP_SET operation with text protocol Check data was set for a key "emptyBytesKey" via MAP_SET: expected false to be true
1bcf3de3-263b-4b48-9feb-d6966b739590 c3be6a68-d463-42b0-996f-4ebac3c7070c should handle different data types in MAP_CREATE operation with binary protocol rest/objects Rest with Objects plugin RestObject.publish() should handle different data types in MAP_CREATE operation with binary protocol Check data was set for a key "emptyBytesKey" via MAP_CREATE: expected false to be true
faa88a5d-71ef-4db6-92de-717fbb32482b ffb6248b-036e-4ed3-b44d-cd2e5ed871cc should handle different data types in MAP_CREATE operation with text protocol rest/objects Rest with Objects plugin RestObject.publish() should handle different data types in MAP_CREATE operation with text protocol Check data was set for a key "emptyBytesKey" via MAP_CREATE: expected false to be true