mdedetrich commented on PR #12675:
URL: https://github.com/apache/kafka/pull/12675#issuecomment-1279749434

   So I have updated the PR with the following changes
   
   * Scala 2.13.10 just came out, so I bumped the Scala version (commit message 
has also been updated)
   * I have added a workaround for the depreciation warning message in the 
commit `Add workaround for change of behaviour in deprecation for 2.13.10`.
   
   The latest CI run has failed but it appears to be due to a possible 
unrelated problem, i.e. the zinc compiler has a timeout because 
kafka-streams-scala was compiling at the same time as core-scala
   
   ```
   [2022-10-15T13:27:03.553Z] BUILD FAILED in 8m 24s
   
   [2022-10-15T13:27:03.553Z] 237 actionable tasks: 192 executed, 45 up-to-date
   
   [2022-10-15T13:27:03.553Z] 
   
   [2022-10-15T13:27:03.553Z] See the profiling report at: 
file:///home/jenkins/workspace/Kafka_kafka-pr_PR-12675/build/reports/profile/profile-2022-10-15-13-18-44.html
   
   [2022-10-15T13:27:03.553Z] A fine-grained performance profile is available: 
use the --scan option.
   
   [2022-10-15T13:27:04.484Z] > Timeout waiting to lock zinc-1.6.1_2.13.10_11 
compiler cache (/home/jenkins/.gradle/caches/7.5.1/zinc-1.6.1_2.13.10_11). It 
is currently in use by another Gradle instance.
   
   [2022-10-15T13:27:04.484Z] Retrying due to zinc lock timeout
   
   [2022-10-15T13:27:05.415Z] To honour the JVM settings for this build a 
single-use Daemon process will be forked. See 
https://docs.gradle.org/7.5.1/userguide/gradle_daemon.html#sec:disabling_the_daemon.
   
   [2022-10-15T13:27:07.178Z] Daemon will be stopped at the end of the build 
   ```
   
   @mimaison @cadonna @ijuma Would it be possible to retrigger the CI so I can 
see if this error is deterministic? If so I will have a look into the problem.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to