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

Aws2-kinesis-firehose: flaky test #6185

Open
JiriOndrusek opened this issue Jun 13, 2024 · 0 comments
Open

Aws2-kinesis-firehose: flaky test #6185

JiriOndrusek opened this issue Jun 13, 2024 · 0 comments
Assignees
Labels
area/testing backport/3.8.x bug Something isn't working flaky-test Issues for tests that are known to be flaky test

Comments

@JiriOndrusek
Copy link
Contributor

Bug description

I encountered a failure during the execution of Aws2KinesisFirehoseTest with real service.

This is the shortened log:

2024-05-29 08:28:51,485 INFO  [org.apa.cam.imp.eng.AbstractCamelContext] (main) Apache Camel (camel-1) is starting
2024-05-29 08:28:51,493 INFO  [org.apa.cam.imp.eng.AbstractCamelContext] (main) Routes startup (started:2)
...(camel-1) started in 7ms (build:0ms init:0ms start:7ms)

2024-05-29 08:28:51,899 INFO  [org.apa.cam.qua.com.aws.kin.it.Aws2KinesisFirehoseTest] (main) Sending 1 MB of data to firehose using chunk ...
...
2024-05-29 08:28:54,547 INFO  [org.apa.cam.qua.com.aws.kin.it.Aws2KinesisFirehoseTest] (main) Sent 1 MB of data to firehose
2024-05-29 08:28:56,175 INFO  [org.apa.cam.qua.com.aws.kin.it.Aws2KinesisTestEnvCustomizer] (main) Deleting 0 objects in bucket camel-quarkus-firehose-jwzjwsyj0ny9xchhorivct584dzge8ra
2024-05-29 08:28:56,258 WARN  [org.apa.cam.qua.tes.sup.aws.Aws2TestEnvContext] (main) Could not close org.apache.camel.quarkus.component.aws2.kinesis.it.Aws2KinesisTestEnvCustomizer$$Lambda/0x00007efcd85ace88@1c33d539: software.amazon.awssdk.services.s3.model.NoSuchBucketException: The specified bucket does not exist (Service: S3, Status Code: 404

From the log, I can see that the test successfully logged message from line 81.
But after that there is a failure from Aws2TestEnvContext and there is no logged message confirming that the awaitility block from the test was executed. (there is not even the 2 minutes delay in the timestamps of the log)

@JiriOndrusek JiriOndrusek added bug Something isn't working test backport/3.8.x labels Jun 13, 2024
@JiriOndrusek JiriOndrusek self-assigned this Jun 13, 2024
@JiriOndrusek JiriOndrusek changed the title Aws2-kinesis-firehosr: flaky test Aws2-kinesis-firehose: flaky test Jun 13, 2024
@jamesnetherton jamesnetherton modified the milestone: 3.12.0 Jun 14, 2024
@jamesnetherton jamesnetherton added the flaky-test Issues for tests that are known to be flaky label Jun 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/testing backport/3.8.x bug Something isn't working flaky-test Issues for tests that are known to be flaky test
Projects
None yet
Development

No branches or pull requests

2 participants