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

[3.15] Backports #2082

Merged
merged 8 commits into from
Oct 10, 2024
Merged

[3.15] Backports #2082

merged 8 commits into from
Oct 10, 2024

Conversation

fedinskiy
Copy link
Contributor

Summary

Backports these PRs:

Please select the relevant options.

  • Bug fix (non-breaking change which fixes an issue)
  • Dependency update
  • Refactoring
  • Backport
  • New scenario (non-breaking change which adds functionality)
  • This change requires a documentation update
  • This change requires execution against OCP (use run tests phrase in comment)

Checklist:

  • Methods and classes used in PR scenarios are meaningful
  • Commits are well encapsulated and follow the best practices

Following the recommendation from quarkusio/quarkus#43360

(cherry picked from commit 64f9986)
@fedinskiy fedinskiy self-assigned this Oct 10, 2024
@fedinskiy
Copy link
Contributor Author

run tests

Copy link
Member

@michalvavrik michalvavrik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@michalvavrik
Copy link
Member

@fedinskiy I think you need to check the Kafka failure

@fedinskiy
Copy link
Contributor Author

@michalvavrik it is backport of your commit (#2060) Any idea, why server.jks may be not generated/found?

@michalvavrik
Copy link
Member

@michalvavrik it is backport of your commit (#2060) Any idea, why server.jks may be not generated/found?

probably backports are not one to one, let me have a look

@michalvavrik
Copy link
Member

@fedinskiy had a look, you picked just one of 2 commits https://github.com/quarkus-qe/quarkus-test-suite/pull/2060/commits you need both; it was intentional to have 2 commits

@fedinskiy
Copy link
Contributor Author

@michalvavrik I backported the merge commit (neither 2046096aefd3679d43e241391e9cd0791362966 nor 46b1641d121a565fe365cf5f08b9f590f356a39a are in our main trunk)

@michalvavrik
Copy link
Member

@michalvavrik I backported the merge commit (neither 2046096aefd3679d43e241391e9cd0791362966 nor 46b1641d121a565fe365cf5f08b9f590f356a39a are in our main trunk)

in that case commit title is wrong. in any case, this only happens when commits doesn't apply, I'll report back

mocenas and others added 7 commits October 10, 2024 16:42
…image

This was discoverd with IBM testing and fixed for 3.8 branch in quarkus-qe#2004

(cherry picked from commit b6e1406)
We have --stream parameter enabled everywhere by default,
but this behavior conflicts with --platform option, we use in several tests

(cherry picked from commit 9aa05cb)
@michalvavrik
Copy link
Member

I still see a difference between these commits. In the main branch PR https://github.com/quarkus-qe/quarkus-test-suite/pull/2060/files I can see kafkaSSL/src/main/java that are completely missing in this PR. Without these changes it cannot work properly.

@fedinskiy
Copy link
Contributor Author

@michalvavrik it looks like github API returns only the last commit id sometimes, if there were several of them. I think I did the proper backport now, Let's try CI again

@michalvavrik
Copy link
Member

sure, thanks

@fedinskiy
Copy link
Contributor Author

run tests

@github-actions github-actions bot added the triage/flaky-test Signal that flaky tests were detected during CI run label Oct 10, 2024
Copy link

Unknown format for flaky report filename: flaky-run-report.json
Following jobs contain at least one flaky test:

  • PR - Linux - JVM build - Latest Version

Run summary: https://github.com/quarkus-qe/quarkus-test-suite/actions/runs/11276415589?pr=2082

Flaky tests:


io.quarkus.ts.messaging.kafka.reactive.streams.KafkaGratefulShutdownIT.testConnection

  • Failure message: Assertion condition defined as a Lambda expression in io.quarkus.test.utils.LogsVerifier Log does not contain any of '[ave]'. Full logs: [__ ____ __ _____ ___ __ ____ ______ , --/ __ \/ / / / _ | / _ \/ //_/ / / / __/ , -/ /_/ / /_/ / __ |/ , _/ ,< / /_/ /\ \ , --\___\_\____/_/ |_/_/|_/_/|_|\____/___/ , 15:47:40,010 SRMSG18229: Configured topics for channel 'slow': [slow], 15:47:40,025 SRMSG18214: Key deserializer omitted, using String as default, 15:47:40,025 SRMSG18234: Auto-commit disabled for channel slow, 15:47:40,205 SRMSG18240: 'throttled' commit strategy used for channel 'slow', 15:47:40,206 SRMSG18232: Will commit for group 'kafka-streams-reactive-messaging' every 5000 milliseconds., 15:47:40,206 SRMSG18236: Will mark throttled commit strategy for group 'kafka-streams-reactive-messaging' as unhealthy if records go more than 60000 milliseconds without being processed., 15:47:40,237 SRMSG18248: Key serializer omitted, using String as default, 15:47:40,264 SRMSG18258: Kafka producer kafka-producer-slow-topic, connected to Kafka brokers 'localhost:32794', is configured to write records to 'slow', 15:47:40,315 SRMSG18257: Kafka consumer kafka-consumer-slow, connected to Kafka brokers 'localhost:32794', belongs to the 'kafka-streams-reactive-messaging' consumer group and is configured to poll records from [slow], 15:47:40,319 No Topology producer; Kafka Streams will not be started, 15:47:40,413 kafka-streams-reactive-messaging 1.0.0-SNAPSHOT on JVM (powered by Quarkus 3.15.999-SNAPSHOT) started in 1.358s. Listening on: http://0.0.0.0:1104, 15:47:40,413 Profile prod activated. , 15:47:40,413 Installed features: [cdi, kafka-client, kafka-streams, messaging, messaging-kafka, resteasy, resteasy-jsonb, smallrye-context-propagation, vertx], 15:47:40,535 [Consumer clientId=kafka-consumer-slow, groupId=kafka-streams-reactive-messaging] Error while fetching metadata with correlation id 2 : {slow=UNKNOWN_TOPIC_OR_PARTITION}, 15:47:44,016 SRMSG18209: Sending message org.eclipse.microprofile.reactive.messaging.Message$5@75609bc8 from channel 'slow-topic' to Kafka topic 'slow', 15:47:44,108 SRMSG18211: Message org.eclipse.microprofile.reactive.messaging.Message$5@75609bc8 from channel 'slow-topic' sent successfully to Kafka topic-partition 'slow-0', with offset 0] ==> expected: <true> but was: <false> within 30 seconds.
  • Failed in jobs:
    • flaky-run-report.json
Failure stacktrace
org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a Lambda expression in io.quarkus.test.utils.LogsVerifier Log does not contain any of '[ave]'. Full logs: [__  ____  __  _____   ___  __ ____  ______ ,  --/ __ \/ / / / _ | / _ \/ //_/ / / / __/ ,  -/ /_/ / /_/ / __ |/ , _/ ,< / /_/ /\ \   , --\___\_\____/_/ |_/_/|_/_/|_|\____/___/   , 15:47:40,010 SRMSG18229: Configured topics for channel 'slow': [slow], 15:47:40,025 SRMSG18214: Key deserializer omitted, using String as default, 15:47:40,025 SRMSG18234: Auto-commit disabled for channel slow, 15:47:40,205 SRMSG18240: 'throttled' commit strategy used for channel 'slow', 15:47:40,206 SRMSG18232: Will commit for group 'kafka-streams-reactive-messaging' every 5000 milliseconds., 15:47:40,206 SRMSG18236: Will mark throttled commit strategy for group 'kafka-streams-reactive-messaging' as unhealthy if records go more than 60000 milliseconds without being processed., 15:47:40,237 SRMSG18248: Key serializer omitted, using String as default, 15:47:40,264 SRMSG18258: Kafka producer kafka-producer-slow-topic, connected to Kafka brokers 'localhost:32794', is configured to write records to 'slow', 15:47:40,315 SRMSG18257: Kafka consumer kafka-consumer-slow, connected to Kafka brokers 'localhost:32794', belongs to the 'kafka-streams-reactive-messaging' consumer group and is configured to poll records from [slow], 15:47:40,319 No Topology producer; Kafka Streams will not be started, 15:47:40,413 kafka-streams-reactive-messaging 1.0.0-SNAPSHOT on JVM (powered by Quarkus 3.15.999-SNAPSHOT) started in 1.358s. Listening on: http://0.0.0.0:1104, 15:47:40,413 Profile prod activated. , 15:47:40,413 Installed features: [cdi, kafka-client, kafka-streams, messaging, messaging-kafka, resteasy, resteasy-jsonb, smallrye-context-propagation, vertx], 15:47:40,535 [Consumer clientId=kafka-consumer-slow, groupId=kafka-streams-reactive-messaging] Error while fetching metadata with correlation id 2 : {slow=UNKNOWN_TOPIC_OR_PARTITION}, 15:47:44,016 SRMSG18209: Sending message org.eclipse.microprofile.reactive.messaging.Message$5@75609bc8 from channel 'slow-topic' to Kafka topic 'slow', 15:47:44,108 SRMSG18211: Message org.eclipse.microprofile.reactive.messaging.Message$5@75609bc8 from channel 'slow-topic' sent successfully to Kafka topic-partition 'slow-0', with offset 0] ==> expected: <true> but was: <false> within 30 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1006)
	at org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:790)
	at io.quarkus.test.utils.AwaitilityUtils.untilAsserted(AwaitilityUtils.java:134)
	at io.quarkus.test.utils.AwaitilityUtils.untilAsserted(AwaitilityUtils.java:124)
	at io.quarkus.test.utils.LogsVerifier.assertContains(LogsVerifier.java:28)
	at io.quarkus.ts.messaging.kafka.reactive.streams.KafkaGratefulShutdownIT.testConnection(KafkaGratefulShutdownIT.java:71)
	at java.base/java.lang.reflect.Method.invoke(Method.java:569)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
Caused by: org.opentest4j.AssertionFailedError: Log does not contain any of '[ave]'. Full logs: [__  ____  __  _____   ___  __ ____  ______ ,  --/ __ \/ / / / _ | / _ \/ //_/ / / / __/ ,  -/ /_/ / /_/ / __ |/ , _/ ,< / /_/ /\ \   , --\___\_\____/_/ |_/_/|_/_/|_|\____/___/   , 15:47:40,010 SRMSG18229: Configured topics for channel 'slow': [slow], 15:47:40,025 SRMSG18214: Key deserializer omitted, using String as default, 15:47:40,025 SRMSG18234: Auto-commit disabled for channel slow, 15:47:40,205 SRMSG18240: 'throttled' commit strategy used for channel 'slow', 15:47:40,206 SRMSG18232: Will commit for group 'kafka-streams-reactive-messaging' every 5000 milliseconds., 15:47:40,206 SRMSG18236: Will mark throttled commit strategy for group 'kafka-streams-reactive-messaging' as unhealthy if records go more than 60000 milliseconds without being processed., 15:47:40,237 SRMSG18248: Key serializer omitted, using String as default, 15:47:40,264 SRMSG18258: Kafka producer kafka-producer-slow-topic, connected to Kafka brokers 'localhost:32794', is configured to write records to 'slow', 15:47:40,315 SRMSG18257: Kafka consumer kafka-consumer-slow, connected to Kafka brokers 'localhost:32794', belongs to the 'kafka-streams-reactive-messaging' consumer group and is configured to poll records from [slow], 15:47:40,319 No Topology producer; Kafka Streams will not be started, 15:47:40,413 kafka-streams-reactive-messaging 1.0.0-SNAPSHOT on JVM (powered by Quarkus 3.15.999-SNAPSHOT) started in 1.358s. Listening on: http://0.0.0.0:1104, 15:47:40,413 Profile prod activated. , 15:47:40,413 Installed features: [cdi, kafka-client, kafka-streams, messaging, messaging-kafka, resteasy, resteasy-jsonb, smallrye-context-propagation, vertx], 15:47:40,535 [Consumer clientId=kafka-consumer-slow, groupId=kafka-streams-reactive-messaging] Error while fetching metadata with correlation id 2 : {slow=UNKNOWN_TOPIC_OR_PARTITION}, 15:47:44,016 SRMSG18209: Sending message org.eclipse.microprofile.reactive.messaging.Message$5@75609bc8 from channel 'slow-topic' to Kafka topic 'slow', 15:47:44,108 SRMSG18211: Message org.eclipse.microprofile.reactive.messaging.Message$5@75609bc8 from channel 'slow-topic' sent successfully to Kafka topic-partition 'slow-0', with offset 0] ==> expected: <true> but was: <false>
	at io.quarkus.test.utils.LogsVerifier.lambda$assertContains$0(LogsVerifier.java:30)
	at org.awaitility.core.AssertionCondition.lambda$new$0(AssertionCondition.java:53)
	at org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:248)
	at org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:235)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.lang.Thread.run(Thread.java:840)


@michalvavrik michalvavrik merged commit fe3768d into quarkus-qe:3.15 Oct 10, 2024
10 checks passed
@fedinskiy fedinskiy deleted the backports/10.10 branch October 11, 2024 06:52
@michalvavrik michalvavrik removed the triage/flaky-test Signal that flaky tests were detected during CI run label Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants