See <https://ci-builds.apache.org/job/Calcite/job/Calcite-snapshots/917/display/redirect?page=changes>
Changes: [Xiong Duan] [CALCITE-6325] Add LOG function (enabled in Mysql and Spark library) ------------------------------------------ Started by GitHub push by NobiGo Started by GitHub push by NobiGo Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on builds23 (ubuntu) in workspace <https://ci-builds.apache.org/job/Calcite/job/Calcite-snapshots/ws/> [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Deferred wipeout is used... [WS-CLEANUP] Done The recommended git tool is: NONE No credentials specified Cloning the remote Git repository Using shallow clone with depth 100 Avoid fetching tags Honoring refspec on initial clone Cloning repository https://github.com/apache/calcite.git > git init > <https://ci-builds.apache.org/job/Calcite/job/Calcite-snapshots/ws/> # > timeout=10 Fetching upstream changes from https://github.com/apache/calcite.git > git --version # timeout=10 > git --version # 'git version 2.34.1' > git fetch --no-tags --force --progress --depth=100 -- > https://github.com/apache/calcite.git +refs/heads/*:refs/remotes/origin/* # > timeout=10 > git config remote.origin.url https://github.com/apache/calcite.git # > timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # > timeout=10 Avoid second fetch > git rev-parse refs/remotes/origin/main^{commit} # timeout=10 Checking out Revision 8ab0b03326730aa2cc6b476b2cbd8f99799bdacb (refs/remotes/origin/main) > git config core.sparsecheckout # timeout=10 > git checkout -f 8ab0b03326730aa2cc6b476b2cbd8f99799bdacb # timeout=10 Commit message: "[CALCITE-6325] Add LOG function (enabled in Mysql and Spark library)" > git rev-list --no-walk cdb6522d3320776f6c7ce66c01747447a39a8c84 # timeout=10 [Gradle] - Launching build. [Calcite-snapshots] $ <https://ci-builds.apache.org/job/Calcite/job/Calcite-snapshots/ws/gradlew> "-Dorg.gradle.jvmargs=-Xmx1024m -XX:MaxMetaspaceSize=512m" -Pasf=true -PCI=true --no-build-cache --profile --no-daemon build publish To honour the JVM settings for this build a single-use Daemon process will be forked. For more on this, please refer to https://docs.gradle.org/8.7/userguide/gradle_daemon.html#sec:disabling_the_daemon in the Gradle documentation. Daemon will be stopped at the end of the build FAILURE: Build failed with an exception. * What went wrong: Gradle could not start your build. > Cannot create service of type BuildSessionActionExecutor using method > LauncherServices$ToolingBuildSessionScopeServices.createActionExecutor() as > there is a problem with parameter #21 of type > BuildLifecycleAwareVirtualFileSystem. > Cannot create service of type BuildLifecycleAwareVirtualFileSystem using method VirtualFileSystemServices$GradleUserHomeServices.createVirtualFileSystem() as there is a problem with parameter #1 of type FileWatchingFilter. > Cannot create service of type FileWatchingFilter using method VirtualFileSystemServices$GradleUserHomeServices.createFileWatchingFilter() as there is a problem with parameter #1 of type GlobalCacheLocations. > Cannot create service of type GlobalCacheLocations using method GradleUserHomeScopeServices.createGlobalCacheLocations() as there is a problem with parameter #1 of type List<GlobalCache>. > Could not create service of type FileAccessTimeJournal using GradleUserHomeScopeServices.createFileAccessTimeJournal(). > Timeout waiting to lock journal cache (/home/jenkins/.gradle/caches/journal-1). It is currently in use by another Gradle instance. Owner PID: 2423616 Our PID: 3313457 Owner Operation: Our operation: Lock file: /home/jenkins/.gradle/caches/journal-1/journal-1.lock * 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 1m 26s Build step 'Invoke Gradle script' changed build result to FAILURE Build step 'Invoke Gradle script' marked build as failure Recording test results ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?
