Flakey test: com.ably.tracking.tests.PublisherAndSubscriberTests > createAndStartPublisherAndSubscriberAndWaitUntilDataEnds #954
Labels
failing-test
Where an automated test is failing either locally or in CI. Perhaps flakey, wrong or bug.
First noticed in https://github.com/ably/ably-asset-tracking-android/actions/runs/4017396909/jobs/6901700322
This is most likely caused by
EnhancedLocationChangedWorker
: it emits every enhanced location updated on the publishers locations flow, but what reaches the subscriber via Ably is controlled by other factors, namely the subscriber resolution. The test is performed by comparing the publisher locations flow (absolutely everything) and the subscribers flow (only what gets sent over Ably). These two cannot be reliably compared.This could be fixed by addressing #913
The text was updated successfully, but these errors were encountered: