kirktrue commented on PR #13990:
URL: https://github.com/apache/kafka/pull/13990#issuecomment-1646378435
@junrao The JDK 11, 17, and 20 test runs output this as their last test
execution:
```
Gradle Test Run :streams:integrationTest > Gradle Test Executor 177 >
StoreQueryIntegrationTest >
shouldQuerySpecificStalePartitionStoresMultiStreamThreadsNamedTopology() PASSED
streams-3: SMOKE-TEST-CLIENT-CLOSED
streams-7: SMOKE-TEST-CLIENT-CLOSED
streams-5: SMOKE-TEST-CLIENT-CLOSED
streams-6: SMOKE-TEST-CLIENT-CLOSED
streams-0: SMOKE-TEST-CLIENT-CLOSED
streams-8: SMOKE-TEST-CLIENT-CLOSED
streams-1: SMOKE-TEST-CLIENT-CLOSED
streams-2: SMOKE-TEST-CLIENT-CLOSED
streams-4: SMOKE-TEST-CLIENT-CLOSED
streams-2: SMOKE-TEST-CLIENT-CLOSED
streams-5: SMOKE-TEST-CLIENT-CLOSED
streams-0: SMOKE-TEST-CLIENT-CLOSED
streams-1: SMOKE-TEST-CLIENT-CLOSED
streams-4: SMOKE-TEST-CLIENT-CLOSED
streams-3: SMOKE-TEST-CLIENT-CLOSED
```
The JDK 11 test run follows that test with the following last lines:
```
Deprecated Gradle features were used in this build, making it incompatible
with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings
and determine if they come from your own scripts or plugins.
For more on this, please refer to
https://docs.gradle.org/8.2.1/userguide/command_line_interface.html#sec:command_line_warnings
in the Gradle documentation.
BUILD SUCCESSFUL in 3h 19m 29s
231 actionable tasks: 124 executed, 107 up-to-date
Publishing build scan...
https://ge.apache.org/s/k4bsfdqsiuqow
See the profiling report at:
file:///home/jenkins/jenkins-agent/workspace/Kafka_kafka-pr_PR-13990/build/reports/profile/profile-2023-07-21-00-27-33.html
A fine-grained performance profile is available: use the --scan option.
Recording test results
[Checks API] No suitable checks publisher found.
Skipping Kafka Streams archetype test for Java 11
```
The JDK 17 test run conclusion is similar, but there's some token publishing
error or something:
```
Deprecated Gradle features were used in this build, making it incompatible
with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings
and determine if they come from your own scripts or plugins.
For more on this, please refer to
https://docs.gradle.org/8.2.1/userguide/command_line_interface.html#sec:command_line_warnings
in the Gradle documentation.
BUILD SUCCESSFUL in 1h 56m 19s
231 actionable tasks: 124 executed, 107 up-to-date
Publishing build scan...
Publishing failed.
The response from https://ge.apache.org/scans/publish/gradle/3.13.4/token
was not from Gradle Enterprise.
The specified server address may be incorrect, or your network environment
may be interfering.
Please report this problem to your Gradle Enterprise administrator via
https://ge.apache.org/help and include the following via copy/paste:
----------
Gradle version: 8.2.1
Plugin version: 3.13.4
Request URL: https://ge.apache.org/scans/publish/gradle/3.13.4/token
Request ID: 97dd78d0-adac-4a90-8f1b-f41b63e6a492
Response status code: 502
Response content type: text/html
----------
See the profiling report at:
file:///home/jenkins/jenkins-agent/workspace/Kafka_kafka-pr_PR-13990/build/reports/profile/profile-2023-07-21-00-24-49.html
A fine-grained performance profile is available: use the --scan option.
Recording test results
[Checks API] No suitable checks publisher found.
Skipping Kafka Streams archetype test for Java 17
```
However, JDK 20 ends with a hard error due to a timeout or something:
```
Sending interrupt signal to process
> Task :clients:unitTest FAILED
The message received from the daemon indicates that the daemon has
disappeared.
Build request sent: Build{id=4413ed42-5d9b-4fcd-94bf-48aaeb0f3abc,
currentDir=/home/jenkins/jenkins-agent/workspace/Kafka_kafka-pr_PR-13990@2}
Attempting to read last messages from the daemon log...
script returned exit code 143
```
I don't have knowledge of the build process and Jenkins enough to know _why_
this is happening. I'll keep digging.
--
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: jira-unsubscr...@kafka.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
