Dzina Dybouskaya

BTW, looks like pr link check is not working: it just checks that there are PR links in the diff, while diff is sth like: ``` diff --git a/CHANGELOG.md b/CHANGELOG.md...

OK, so there is a version that supports API 33: 1.5.0-alpha2 (https://github.com/android/android-test/issues/1412#issuecomment-1227563734) but it requires Kotlin 1.7. As far as I understand, we are not ready to bump that one...

So we can't update to the latest version of androidx test runner which supports API 33 just yet. It only means we cannot run tests on devices with API 33,...

Workaround PR: https://github.com/mapbox/mapbox-navigation-android/pull/6319 After that the issue goes in "To Track" because we wait until we can bump kotlin to 1.7.

As I understand it, it fails by timeout. Maybe some emulators are lagging but we'd need to investigate further.

> As far as I understand this ticket, @dzinad please correct me if you meant something different, we need to apply a different approach for handling of flaky instrumentation test....

Seems like failures are fixed. However, in several PRs I get "inconclusive" results. Does anybody know what to do with it? @mapbox/navigation-android Example: https://circleci.com/gh/mapbox/mapbox-navigation-android/94624?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link

> I think we can ignore the inconclusive results (or re-run a job if needed). But this way we won't be able to make the build required. Because the build...

I noticed it in 2 of 5 of my PRs. But the most recent ones. Maybe it's a new issue. Let's observe for some time.

Fixed by https://github.com/mapbox/mapbox-navigation-android/pull/6334.