https://kotlinlang.org logo
Channels
100daysofcode
100daysofkotlin
100daysofkotlin-2021
advent-of-code
aem
ai
alexa
algeria
algolialibraries
amsterdam
android
android-architecture
android-databinding
android-studio
androidgithubprojects
androidthings
androidx
androidx-xprocessing
anime
anko
announcements
apollo-kotlin
appintro
arabic
argentina
arkenv
arksemdevteam
armenia
arrow
arrow-contributors
arrow-meta
ass
atlanta
atm17
atrium
austin
australia
austria
awesome-kotlin
ballast
bangladesh
barcelona
bayarea
bazel
beepiz-libraries
belgium
benchmarks
berlin
big-data
books
boston
brazil
brikk
budapest
build
build-tools
bulgaria
bydgoszcz
cambodia
canada
carrat
carrat-dev
carrat-feed
chicago
chile
china
chucker
cincinnati-user-group
cli
clikt
cloudfoundry
cn
cobalt
code-coverage
codeforces
codemash-precompiler
codereview
codingame
codingconventions
coimbatore
collaborations
colombia
colorado
communities
competitive-programming
competitivecoding
compiler
compose
compose-android
compose-desktop
compose-hiring
compose-ios
compose-mp
compose-ui-showcase
compose-wear
compose-web
confetti
connect-audit-events
corda
cork
coroutines
couchbase
coursera
croatia
cryptography
cscenter-course-2016
cucumber-bdd
cyprus
czech
dagger
data2viz
databinding
datascience
dckotlin
debugging
decompose
decouple
denmark
deprecated
detekt
detekt-hint
dev-core
dfw
docs-revamped
dokka
domain-driven-design
doodle
dsl
dublin
dutch
eap
eclipse
ecuador
edinburgh
education
effective-kotlin
effectivekotlin
emacs
embedded-kotlin
estatik
event21-community-content
events
exposed
failgood
fb-internal-demo
feed
firebase
flow
fluid-libraries
forkhandles
forum
fosdem
fp-in-kotlin
framework-elide
freenode
french
fritz2
fuchsia
functional
funktionale
gamedev
ge-kotlin
general-advice
georgia
geospatial
german-lang
getting-started
github-workflows-kt
glance
godot-kotlin
google-io
gradle
graphic
graphkool
graphql
graphql-kotlin
graviton-browser
greece
grpc
gsoc
gui
hackathons
hacktoberfest
hamburg
hamkrest
helios
helsinki
hexagon
hibernate
hikari-cp
hire-me
hiring
hiring-french
hongkong
hoplite
http4k
hungary
hyderabad
image-processing
india
indonesia
inkremental
intellij
intellij-plugins
intellij-tricks
internships
introduce-yourself
io
ios
iran
israel
istanbulcoders
italian
jackson-kotlin
jadx
japanese
jasync-sql
java-to-kotlin-refactoring
javadevelopers
javafx
javalin
javascript
jdbi
jhipster-kotlin
jobsworldwide
jpa
jshdq
juul-libraries
jvm-ir-backend-feedback
jxadapter
k2-early-adopters
kaal
kafka
kakao
kalasim
kapt
karachi
karg
karlsruhe
kash_shell
kaskade
kbuild
kdbc
kgen-doc-tools
kgraphql
kinta
klaxon
klock
kloudformation
kmdc
kmm-español
kmongo
knbt
knote
koalaql
koans
kobalt
kobweb
kodein
kodex
kohesive
koin
koin-dev
komapper
kondor-json
kong
kontent
kontributors
korau
korean
korge
korim
korio
korlibs
korte
kotest
kotest-contributors
kotless
kotlick
kotlin-asia
kotlin-beam
kotlin-by-example
kotlin-csv
kotlin-data-storage
kotlin-foundation
kotlin-fuel
kotlin-in-action
kotlin-inject
kotlin-latam
kotlin-logging
kotlin-multiplatform-contest
kotlin-mumbai
kotlin-native
kotlin-pakistan
kotlin-plugin
kotlin-pune
kotlin-roadmap
kotlin-samples
kotlin-sap
kotlin-serbia
kotlin-spark
kotlin-szeged
kotlin-website
kotlinacademy
kotlinbot
kotlinconf
kotlindl
kotlinforbeginners
kotlingforbeginners
kotlinlondon
kotlinmad
kotlinprogrammers
kotlinsu
kotlintest
kotlintest-devs
kotlintlv
kotlinultimatechallenge
kotlinx-datetime
kotlinx-files
kotlinx-html
kotrix
kotson
kovenant
kprompt
kraph
krawler
kroto-plus
ksp
ktcc
ktfmt
ktlint
ktor
ktp
kubed
kug-leads
kug-torino
kvision
kweb
lambdaworld_cadiz
lanark
language-evolution
language-proposals
latvia
leakcanary
leedskotlinusergroup
lets-have-fun
libgdx
libkgd
library-development
lincheck
linkeddata
lithuania
london
losangeles
lottie
love
lychee
macedonia
machinelearningbawas
madrid
malaysia
mathematics
meetkotlin
memes
meta
metro-detroit
mexico
miami
micronaut
minnesota
minutest
mirror
mockk
moko
moldova
monsterpuzzle
montreal
moonbean
morocco
motionlayout
mpapt
mu
multiplatform
mumbai
munich
mvikotlin
mvrx
myndocs-oauth2-server
naming
navigation-architecture-component
nepal
new-mexico
new-zealand
newname
nigeria
nodejs
norway
npm-publish
nyc
oceania
ohio-kotlin-users
oldenburg
oolong
opensource
orbit-mvi
osgi
otpisani
package-search
pakistan
panamá
pattern-matching
pbandk
pdx
peru
philippines
phoenix
pinoy
pocketgitclient
polish
popkorn
portugal
practical-functional-programming
proguard
prozis-android-backup
pyhsikal
python
python-contributors
quasar
random
re
react
reaktive
realm
realworldkotlin
reductor
reduks
redux
redux-kotlin
refactoring-to-kotlin
reflect
refreshversions
reports
result
rethink
revolver
rhein-main
rocksdb
romania
room
rpi-pico
rsocket
russian
russian_feed
russian-kotlinasfirst
rx
rxjava
san-diego
science
scotland
scrcast
scrimage
script
scripting
seattle
serialization
server
sg-user-group
singapore
skia-wasm-interop-temp
skrape-it
slovak
snake
sofl-user-group
southafrica
spacemacs
spain
spanish
speaking
spek
spin
splitties
spotify-mobius
spring
spring-security
squarelibraries
stackoverflow
stacks
stayhungrystayfoolish
stdlib
stlouis
strife-discord-lib
strikt
students
stuttgart
sudan
swagger-gradle-codegen
swarm
sweden
swing
swiss-user-group
switzerland
talking-kotlin
tallinn
tampa
teamcity
tegal
tempe
tensorflow
terminal
test
testing
testtestest
texas
tgbotapi
thailand
tornadofx
touchlab-tools
training
tricity-kotlin-user-group
trójmiasto
truth
tunisia
turkey
turkiye
twitter-feed
uae
udacityindia
uk
ukrainian
uniflow
unkonf
uruguay
utah
uuid
vancouver
vankotlin
vertx
videos
vienna
vietnam
vim
vkug
vuejs
web-mpp
webassembly
webrtc
wimix_sentry
wwdc
zircon
Powered by
Title
m

Marcelo Hernandez

04/10/2023, 9:01 PM
Hello. Has anyone been able to successfully run
./gradlew iosSimulatorArm64Test
in GitHub Actions without any tests getting skipped? I have tests in
commonTest
and even if I intentionally make a test fail, it will appear to "pass" in CI but it's as if the tests are skipped. The reverse is true for
./gradlew iosX64Test
where it runs successfully in GitHub Actions (the test fails as expected) but gets skipped on my local dev machine (M1 Mac).
j

jw

04/10/2023, 9:06 PM
That seems to be exactly what I'd expect
h

hfhbd

04/10/2023, 9:06 PM
iosX64 requires an Intel cpu, while iosArm64 requires an Apple Silicon (M1) cpu. Github uses Intel cpu, so these tests are skipped as expected.
j

jw

04/10/2023, 9:07 PM
You can't run an architecture on a different one without emulation
Also note that GitHub announced arm mac's are coming
But if you really need to test both architectures you'll need two jobs
m

Marcelo Hernandez

04/10/2023, 9:10 PM
Thank you for the clarification. I figured that's where things were headed. I was hoping to have some form of consistency where if a test fails in CI, developers can easily reproduce on their local machines and troubleshoot accordingly. We're just starting to dabble with KMM so this is all kinda new for us. 🙂
h

hfhbd

04/10/2023, 9:11 PM
Yeah, Github arm support should come, but it was moved very often to the future: https://github.com/orgs/github/projects/4247?pane=issue&itemId=5944419
m

Marcelo Hernandez

04/10/2023, 9:15 PM
And by "us", I mean the Android team 😄
Thank you @jw and @hfhbd!
j

jw

04/10/2023, 9:35 PM
It should be rare that you have a failure in one architecture but not another
m

Marcelo Hernandez

04/10/2023, 9:48 PM
I was hoping to have some form of consistency where if a test fails in CI, developers can easily reproduce on their local machines and troubleshoot accordingly.
One solution my teammate suggested was to have a custom
iosTest
task that acts as an alias for either
iosX64Test
if running in CI or
iosSimulatorArm64Test
if not.
j

jw

04/10/2023, 9:49 PM
If you are using hierarchical source sets that task already exists and will run both, and then only one will actually run
m

Marcelo Hernandez

04/10/2023, 9:53 PM
Oh sweet! I'll check it out.
So I'm following the Kotlin Gradle snippet from https://kotlinlang.org/docs/multiplatform-hierarchy.html#target-shortcuts-and-arm64-apple-silicon-simulators, but when I try to run the
iosTest
task, I get the error indicating that that task does not exist
* What went wrong:
Task 'iosTest' not found in root project '*****' and its subprojects. Some candidates are: 'iosX64Test', 'jvmTest', 'test'.
When I run the
tasks
task on one of my KMM modules, the only tasks that show up under
Verification tasks
are
Verification tasks
------------------
allTests - Runs the tests for all targets and create aggregated report
check - Runs all checks.
iosSimulatorArm64Test - Executes Kotlin/Native unit tests for target iosSimulatorArm64.
iosX64Test - Executes Kotlin/Native unit tests for target iosX64.
jvmTest - Runs the tests of the test test run.
h

hfhbd

04/11/2023, 5:08 PM
ios() doesn’t contain the simulator target, you have to add this target manually.
m

Marcelo Hernandez

04/11/2023, 5:08 PM
Correct. From the snippet in the link I referenced above, it explicitly adds
iosSimulatorArm64()
below
ios()
. Which is what I'm also doing.
h

hfhbd

04/11/2023, 5:09 PM
Okay, but you need to add it to the source set hierarchy manually too.
j

jw

04/11/2023, 5:09 PM
You'll want to use the new natural hierarchy DSL if you can
it shipped in 1.8.20
m

Marcelo Hernandez

04/11/2023, 5:10 PM
Ah, okay. I'm still on 1.8.10.
h

hfhbd

04/11/2023, 5:10 PM
I guess this experimental function isn’t documented well 😐
j

jw

04/11/2023, 5:11 PM
you can always build it up yourself manually
m

Marcelo Hernandez

04/11/2023, 5:11 PM
FWIW, here is my configuration
kotlin {
  applyKotlinMultiplatformConfiguration() // This just setting explicit API mode

  ios()
  // Add the ARM64 simulator target
  iosSimulatorArm64()

  val iosMain by sourceSets.getting
  val iosTest by sourceSets.getting
  val iosSimulatorArm64Main by sourceSets.getting
  val iosSimulatorArm64Test by sourceSets.getting

  // Set up dependencies between the source sets
  iosSimulatorArm64Main.dependsOn(iosMain)
  iosSimulatorArm64Test.dependsOn(iosTest)
}
h

hfhbd

04/11/2023, 5:13 PM
This looks correct and should work 🤔
m

Marcelo Hernandez

04/11/2023, 5:14 PM
Meaning an
iosTest
Gradle task should exist yes?
The `iosTest`/`iosMain` source sets work as expected. It's just that as far as the test tasks that are available, I only see
iosSimulatorArm64Test
and
iosX64Test
as the specific test tasks that pertain to iOS.
Another approach was to create a custom
iosTest
task like so
tasks.register("iosTest") {
  group = "Verification"
  description = "An alias for iosX64Test if running in CI; otherwise iosSimulatorArm64Test."
  dependsOn(
      // GitHub Actions uses Intel CPU in their Mac images. Trying to run iosSimulatorArm64Test
      // (arm64 tests) in CI results in the tests silently getting skippped rather than the build
      // failing. The reverse is true for our dev machines (assuming M1 chip) where tests from
      // iosX64Test get silently skipped.
      if (System.getenv("CI") != null) {
        "iosX64Test"
      } else {
        "iosSimulatorArm64Test"
      })
}
This appears to be working for me and there is no task name clash.
h

hfhbd

04/11/2023, 5:20 PM
This definitely works, but afaik there should be a predefined task.
m

Marcelo Hernandez

04/11/2023, 5:23 PM
I'll keep digging. Thanks for the help 🙂