Slow build and failed tests

I am trying to have 1st build of KaMPKit. I was able to successfully build and run it in Android Studio.

Now I am trying to run 1st optional step of iOS build. I have already downloaded and run XCode 11.5.

For unknown reasons the build takes too long and all tests are failing.

Just in case I am running the build on MacBook Pro 16" (2019), MacOS Catalina 10.15.4.

$ ./gradlew clean build
> Task :shared:testReleaseUnitTest

...

> Task :shared:testReleaseUnitTest

co.touchlab.kampkit.KoinTest > checkAllModules FAILED
    org.apache.tools.ant.BuildException
        Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException

co.touchlab.kampkit.ConcurrencyTest > testMain FAILED
    org.apache.tools.ant.BuildException
        Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException

co.touchlab.kampkit.BreedModelTest > updateFavoriteTest FAILED
    org.apache.tools.ant.BuildException
        Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException

co.touchlab.kampkit.BreedModelTest > notifyErrorOnException FAILED
    org.apache.tools.ant.BuildException
        Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException

co.touchlab.kampkit.BreedModelTest > staleDataCheckTest FAILED
    org.apache.tools.ant.BuildException
        Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException

co.touchlab.kampkit.SqlDelightTest > Select All Items Success FAILED
    org.apache.tools.ant.BuildException
        Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException

co.touchlab.kampkit.SqlDelightTest > Update Favorite Success FAILED
    org.apache.tools.ant.BuildException
        Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException

co.touchlab.kampkit.SqlDelightTest > Select Item by Id Success FAILED
    org.apache.tools.ant.BuildException
        Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException

co.touchlab.kampkit.SqlDelightTest > Delete All Success FAILED
    org.apache.tools.ant.BuildException
        Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException

9 tests completed, 9 failed

> Task :shared:testReleaseUnitTest FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':shared:testReleaseUnitTest'.
> There were failing tests. See the report at: file:///Users/otrotsenko/dev/repos/3rd_party/kmp/KaMPKit/shared/build/reports/tests/testReleaseUnitTest/index.html

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 47m 53s

And then in the index.html for each test I see the same:

Unable to resolve artifact: Missing:
----------
1) org.robolectric:android-all:jar:4.1.2_r1-robolectric-r1

  Try downloading the file manually from the project website.

  Then, install it using the command: 
      mvn install:install-file -DgroupId=org.robolectric -DartifactId=android-all -Dversion=4.1.2_r1-robolectric-r1 -Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
      mvn deploy:deploy-file -DgroupId=org.robolectric -DartifactId=android-all -Dversion=4.1.2_r1-robolectric-r1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
  	1) org.apache.maven:super-pom:pom:2.0
  	2) org.robolectric:android-all:jar:4.1.2_r1-robolectric-r1

----------
1 required artifact is missing.

for artifact: 
  org.apache.maven:super-pom:pom:2.0

from the specified remote repositories:
  adeya.central (https://nexus.adeya.ch/content/repositories/adeya.central/)


	at org.apache.maven.artifact.ant.DependenciesTask.doExecuteResolution(DependenciesTask.java:268)

[kpgalligan]

This is all Android/JVM side stuff. testReleaseUnitTest is an Android thing, as is org.robolectric:android-all:jar:4.1.2_r1-robolectric-r1. I think best move at this point is to see if 1.4 improves the situation.

[samhill303]

@AlexTrotsenko That seems reasonable, just wouldn’t want to make it too short and get flaky tests