You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GitHub action is still misbehaving with our unit tests running on macOS (times out as never started).
Sometimes it passes for the first time, sometimes it times out, and when re-tried it passes.
It's hard to tell even, when it's fixed, as the former attempt of fixing (to not to use code signing) passed the first time, but then it failed on another PR.
Since we are running the very same unit tests on iPhone simulator, which gives us the code coverage, I am proposing to turn them off for macOS, as it's a duplicate run of the exact same tests. The macOS run of them is currently giving us certainly more pain then benefits.
Note: We are still building the app for macOS as part of this process, we just would not run the unit-tests again.
The text was updated successfully, but these errors were encountered:
Also it seems to me that GH Action is using some virtual env. magic, which is really slow.
For comparison a clean build on M1 of the macOS Kiwix app is under 30 sec, on GH Action it takes over 3 minutes!
GitHub action is still misbehaving with our unit tests running on macOS (times out as never started).
Sometimes it passes for the first time, sometimes it times out, and when re-tried it passes.
It's hard to tell even, when it's fixed, as the former attempt of fixing (to not to use code signing) passed the first time, but then it failed on another PR.
Latest example PR for this:
https://github.com/kiwix/kiwix-apple/actions/runs/12833615870
It failed 3 times, while passed the 4th time without any new commits!
Other GH action users were also complaining about similar issues:
actions/runner-images#6098
Since we are running the very same unit tests on iPhone simulator, which gives us the code coverage, I am proposing to turn them off for macOS, as it's a duplicate run of the exact same tests. The macOS run of them is currently giving us certainly more pain then benefits.
Note: We are still building the app for macOS as part of this process, we just would not run the unit-tests again.
The text was updated successfully, but these errors were encountered: