CI: investigate and fix the failing integration tests job

Create issue
Issue #1152 resolved
Denis Konovalyenko created an issue

Reduced exception information:

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project okapi-it-okapi: Could not resolve dependencies for project net.sf.okapi.it:okapi-it-okapi:jar:1.44.0-SNAPSHOT: Could not find artifact net.sf.okapi.lib:okapi-lib-serialization:jar:1.44.0-SNAPSHOT
...
Caused by: org.apache.maven.project.DependencyResolutionException: Could not resolve dependencies for project net.sf.okapi.it:okapi-it-okapi:jar:1.44.0-SNAPSHOT: Could not find artifact net.sf.okapi.lib:okapi-lib-serialization:jar:1.44.0-SNAPSHOT
...
Caused by: org.eclipse.aether.resolution.DependencyResolutionException: Could not find artifact net.sf.okapi.lib:okapi-lib-serialization:jar:1.44.0-SNAPSHOT
...
Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Could not find artifact net.sf.okapi.lib:okapi-lib-serialization:jar:1.44.0-SNAPSHOT
...
Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact net.sf.okapi.lib:okapi-lib-serialization:jar:1.44.0-SNAPSHOT

For the full stack of exception details please refer to this job log in the context of this pipeline.

Comments (6)

  1. Jim Hargrave Work

    The maven Protobuffers plugin wants the “compile“ phase to generate sources from the protobuf files. Not sure why the plugin does use the “generate-sources“ phase. Anyway, not sure if this is the fix for the CI but I added it to our build.sh just in case to force the generation of all the protobuf sources.

  2. Jim Hargrave Work

    @Chase Tingley @DenisKonovalyenko @Mihai Nita

    I’ve played with this but no luck. lib-serialization is getting deployed as a snapshot so should be accessible. Of course everything works locally. Any help fixing this would really be appreciated. thanks!

  3. Denis Konovalyenko reporter

    @Jim Hargrave Work , I think I was able to mimic the failure:

    $ mvn verify -f integration-tests/okapi/ -P integration
    OpenJDK 64-Bit Server VM warning: Ignoring option MaxPermSize; support was removed in 8.0
    [INFO] Scanning for projects...
    [INFO] ------------------------------------------------------------------------
    [INFO] Detecting the operating system and CPU architecture
    [INFO] ------------------------------------------------------------------------
    [INFO] os.detected.name: freebsd
    [INFO] os.detected.arch: x86_64
    [INFO] os.detected.bitness: 64
    [INFO] os.detected.version: 12.3
    [INFO] os.detected.version.major: 12
    [INFO] os.detected.version.minor: 3
    [INFO] os.detected.classifier: freebsd-x86_64
    [INFO] 
    [INFO] -------------------< net.sf.okapi.it:okapi-it-okapi >-------------------
    [INFO] Building Okapi Integration Tests - Okapi 1.44.0-SNAPSHOT
    [INFO] --------------------------------[ jar ]---------------------------------
    [WARNING] The POM for net.sf.okapi.lib:okapi-lib-serialization:jar:1.44.0-SNAPSHOT is missing, no dependency information available
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD FAILURE
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time:  2.591 s
    [INFO] Finished at: 2022-08-03T23:53:42+03:00
    [INFO] ------------------------------------------------------------------------
    [ERROR] Failed to execute goal on project okapi-it-okapi: Could not resolve dependencies for project net.sf.okapi.it:okapi-it-okapi:jar:1.44.0-SNAPSHOT: Could not find artifact net.sf.okapi.lib:okapi-lib-serialization:jar:1.44.0-S
    

    by the following steps:

    1. mvn clean install -DskipTests # speed up the build a bit
    2. rm -R ~/.m2/repository/net/sf/okapi/lib/okapi-lib-serialization # remove the lib from the repo, should be adjusted to reflect the path in your system
    3. mvn verify -f integration-tests/okapi/ -P integration

    So, it looks like there is something going on with CI cache (.m2/repository folder)…

  4. Log in to comment