Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

com.hazelcast.jet.kafka.connect.KafkaConnectIT.test_scaling #26276

Closed
Patras3 opened this issue Mar 4, 2024 · 2 comments
Closed

com.hazelcast.jet.kafka.connect.KafkaConnectIT.test_scaling #26276

Patras3 opened this issue Mar 4, 2024 · 2 comments

Comments

@Patras3
Copy link
Contributor

Patras3 commented Mar 4, 2024

master (commit 5764f01c5e4d7d2b1dc728eb3e1bbdd716a9c8f7)

Failed on oracle-17 (force-offload): https://jenkins.hazelcast.com/job/Hazelcast-master-force-offload/88/testReport/com.hazelcast.jet.kafka.connect/KafkaConnectIT/test_scaling/

Stacktrace:
java.lang.AssertionError: 

Expecting actual:
  0L
to be greater than:
  1000L

	at com.hazelcast.jet.kafka.connect.KafkaConnectIT.lambda$test_scaling$4(KafkaConnectIT.java:292)
	at com.hazelcast.test.HazelcastTestSupport.assertTrueEventually(HazelcastTestSupport.java:1200)
	at com.hazelcast.test.HazelcastTestSupport.assertTrueEventually(HazelcastTestSupport.java:1305)
	at com.hazelcast.jet.kafka.connect.KafkaConnectIT.test_scaling(KafkaConnectIT.java:291)
	at java.base/java.lang.reflect.Method.invoke(Method.java:568)
	at com.hazelcast.test.FailOnTimeoutStatement$CallableStatement.call(FailOnTimeoutStatement.java:115)
	at com.hazelcast.test.FailOnTimeoutStatement$CallableStatement.call(FailOnTimeoutStatement.java:107)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.lang.Thread.run(Thread.java:842)

Standard output can be found here - https://s3.console.aws.amazon.com/s3/buckets/j-artifacts/Hazelcast-master-force-offload/88/

@Patras3 Patras3 added this to the 5.5 Backlog milestone Mar 4, 2024
@AyberkSorgun AyberkSorgun modified the milestones: 5.5 Backlog, 5.5.0 Apr 8, 2024
@orcunc
Copy link
Contributor

orcunc commented May 2, 2024

I am closing this issue for now after the PR is merged. Let's see if it repeats again

@orcunc orcunc closed this as completed May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants