Building on MacOS is flaky #307
Comments
|
Chrome is available on the runner: https://github.com/actions/runner-images/blob/macos-14-arm64/20241211.616/images/macos/macos-14-arm64-Readme.md#browsers What's more, it works fine in PRs. |
|
We had just a few flakes so far. I'd wait a week or so to see how it behaves. |
|
The issue seems to be gone, no sign of it in the last 2 weeks. |
|
It looks like it reproduced again: |
|
Checking the included software on the worker: https://github.com/actions/runner-images/blob/macos-14-arm64/20250106.725/images/macos/macos-14-arm64-Readme.md Browsers
Environment variables
|
|
Asked the community: https://kotlinlang.slack.com/archives/C3PQML5NU/p1736430268539669. Generally starting from Kotlin's side, before asking GitHub for help. |
|
Looks like this is the cause of the problem:
Maybe for some reason, starting Chrome sometimes takes longer than usual. We can try to increase captureTimeout to see if it solves the problem. |
This should help to reduce failures related to the #307 issue. Also, this change moves karma config to the [correct location](https://karma-runner.github.io/6.4/config/configuration-file.html) - it did not have any effect before that
|
It's still happening :( https://github.com/krzema12/snakeyaml-engine-kmp/actions/runs/12830137762/job/35777664145 |
|
Looks like the configuration was not applied
But it should be 120000 ms now... I will take a look |
|
Looks like we might need to tweak one more option - browserSocketTimeout. Apperantly, it might also cause error like we see in the logs |
There is one more parameter that can help reduce the chances of getting error: > ChromeHeadless has not captured in 60000 ms, killing. Related to #307
Last time we had an error during test execution on macOS we saw that the
**captureTimeout** parameter was not applied. This happened because the
content of `karma.config.d/karma.conf.js` file was merged into the
following block:
```js
module.exports = function(config) {
// kotlin configuration
// ...
// content from our file
}
```
As a result, it looked like this:
```js
module.exports = function(config) {
// kotlin configuration
// ...
// content from our file
module.exports = function(config) {
}
}
```
That was the reason, why our configuration changes were not applied.
Let's see what happens with #307 issue after we correct the
`karma.conf.js`
Sometimes, more than less often, build-on-MacOSLatest fails.
Example: https://github.com/krzema12/snakeyaml-engine-kmp/actions/runs/12377077417/job/34545763964
From the logs:
Several commits earlier, it succeeded: https://github.com/krzema12/snakeyaml-engine-kmp/actions/runs/12369132747/job/34520445069
The text was updated successfully, but these errors were encountered: