Skip to content

Commit 9d4d2d4

Browse files
committed
Exclude x86_64 macOS from the seeding tests.
Running the seeding tests using the "native" ODK setup takes about: * 18 to 22 minutes on the x86_64 GNU/Linux (Ubuntu) runners; * 15 to 18 minutes on the arm64 macOS runners; * 35 to 40 minutes on the x86_64 macOS runners. So for some reason, it takes twice as much time to run the seeding tests on x86_64 macOS than on arm64 macOS. Given how few people seem to use the ODK on x86_64 macOS machines, systematically testing the native ODK setup for this platform does not seem worth it -- it is expected that very few ODK users will ever use the native setup anyway (Docker remains the primary way of using the ODK, at least for now), so the intersection of "ODK users on x86_64 macOS" and "ODK users willing to use the native setup" might very well be the empty set. The native setup will still be _supported_ (for now?) on x86_64 macOS -- it will just not be _tested_ as much as for the x86_64 GNU/Linux and arm64 macOS platforms.
1 parent f0f56e1 commit 9d4d2d4

1 file changed

Lines changed: 6 additions & 3 deletions

File tree

.github/workflows/seed-tests.yml

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -23,9 +23,12 @@ jobs:
2323
strategy:
2424
matrix:
2525
# We run the seeding tests using a "native" ODK environments;
26-
# those will never be supported on Windows, but they SHOULD
27-
# work on x86 GNU/Linux and both x86 and arm64 macOS.
28-
os: [ ubuntu-latest, macos-15, macos-15-intel ]
26+
# those will never be supported on Windows, but they SHOULD work
27+
# on x86 GNU/Linux and both x86 and arm64 macOS.
28+
# However we do NOT routinely test on x64 macOS because GitHub
29+
# Actions runners for that platform are twice slower than the
30+
# the runners for arm64 macOS, and it is just not worth it.
31+
os: [ ubuntu-latest, macos-15 ]
2932
steps:
3033
- name: Check out the repository
3134
uses: actions/checkout@v4

0 commit comments

Comments
 (0)