Are there certain OS packages that would need to be installed for Desktop Compose UI tests to run? E...

# compose-desktop

[eygraber]

Are there certain OS packages that would need to be installed for Desktop Compose UI tests to run? Everything works fine on my local machine, but on CI (GitHub Actions) the tests are flaky in a PR that doesn't change anything test related (sometimes one test fails, sometimes they all fail) - https://github.com/eygraber/vice/pull/131

I tried running without build and configuration caches, and with --rerun-tasks but it still didn't work.

[eygraber]

https://youtrack.jetbrains.com/issue/CMP-5783/Flaky-tests-when-running-Compose-UI-test-on-Desktop-in-a-CI-environment

[Carter]

I’ve had success with this

- name: Setup Xvfb
        timeout-minutes: 3
        run: |
          sudo apt-get update
          sudo apt-get install -y xvfb x11-xserver-utils
      - name: Test
        timeout-minutes: 10
        run: |
          xvfb-run --auto-servernum ./gradlew check

[eygraber]

Thanks, I'll try that out. Is there any overhead to running with xvfb-run?

[Carter]

I haven’t noticed any

[ephemient]

you could launch Xvfb from within Gradle too https://kotlinlang.slack.com/archives/C0B8MA7FA/p1675673380908419?thread_ts=1675662119.934169&cid=C0B8MA7FA

[eygraber]

xvfb-run worked...until the next PR I created where I started getting the same flakiness. So I added the magic --no-build-cache --no-configuration-cache --rerun-tasks and then it worked...until I removed that and now it is flaky again 🙈

[eygraber]

I'm going to x-post to #gradle because there's something weird going on with the caching here.

[suresh]

@ephemient why do we need object { override fun toString() = xvfbServer.get().display } ..to make things lazy ?

[ephemient]

yes

[ephemient]

at least until https://github.com/gradle/gradle/issues/4224

[Eddy Butcher]

Hey @eygraber, sorry to tag directly, did you manage to make any progress here? We've been using cmp in prod for a while on ios/android and use desktop to run ui tests as they are really fast locally, but get tons of flakiness on CI which is slowing us down

[eygraber]

I don't remember, but I'm pretty sure I just stopped doing UI testing in compose desktop because of this.