I'm randomly getting the below issue on MacOS GitHub Actions workers. Do you know why is it happenin...

# multiplatform

[Piotr Krzemiński]

I'm randomly getting the below issue on MacOS GitHub Actions workers. Do you know why is it happening? I checked that the worker does have Chrome for Testing: https://github.com/krzema12/snakeyaml-engine-kmp/issues/307#issuecomment-2580201716

:jsBrowserTest: java.lang.IllegalStateException: Errors occurred during launch of browser for testing.
For more on this, please refer to <https://docs.gradle.org/8.11.1/userguide/command_line_interface.html#sec:command_line_warnings> in the Gradle documentation.
  - ChromeHeadless
  Please make sure that you have installed browsers.
  Or change it via
  browser {
      testTask {
          useKarma {
              useFirefox()
              useChrome()
              useSafari()
          }
      }
  }

[Piotr Krzemiński]

I'm starting investigating this issue from Kotlin side, to understand if there's some non-determinism in detecting the browser

[Mărcuţ Andrei]

your job is running on macos-lasted which has 7GB ram, generally speaking the non-mac runners have larger RAM, I would try macos-13 to run on the previous vm with 14GB ram.

[jw]

macos 13 is also slow as hell because its x86

[Piotr Krzemiński]

I think I'll disable all non-MacOS-specific targets on the MacOS runner - should be safe right? the JS/WASM tests run on Ubuntu and Windows anyway

[Mărcuţ Andrei]

I would keep at least Safari

[Mărcuţ Andrei]

it also depends on how much shared code is covered by the other platforms

[Mărcuţ Andrei]

you should know best

[Piotr Krzemiński]

what's bugging me is that 1 minute is not enough to start and detect Chrome:

ChromeHeadless has not captured in 60000 ms, killing.

right now we test only against Chrome, adding other browsers is TBD

[Mărcuţ Andrei]

I suspect the root cause is low memory on the VM and probably absence of a swapfile, this could prevent spawning additional processes, and the gradle build system does spawn quite some, while the OS itself has to use some RAM as well to run.

[Mărcuţ Andrei]

it’s a sporadic occurrence, might be happening in-between freeing memory, race condition