[
https://issues.apache.org/jira/browse/KAFKA-15986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Schofield resolved KAFKA-15986.
--
Resolution: Fixed
> New consumer group protocol integration test failu
Andrew Schofield created KAFKA-15986:
Summary: New consumer group protocol integration test failures
Key: KAFKA-15986
URL: https://issues.apache.org/jira/browse/KAFKA-15986
Project: Kafka
That’s exactly what I was
> looking for.
>
> Did we track builds before July 12? I see only tiny blips of failures on the
> 90-day view.
>
> Thanks,
> Kirk
>
>> On Jul 26, 2023, at 2:08 AM, Divij Vaidya wrote:
>>
>> Hi Kirk
>>
>> I ha
8 AM, Divij Vaidya wrote:
> >
> > Hi Kirk
> >
> > I have been using this new tool to analyze the trends of test
> > failures:
> > https://ge.apache.org/scans/tests?search.relativeStartTime=P28D=kafka=Europe/Berlin
> > and general build failures:
> &
have been using this new tool to analyze the trends of test
> failures:
> https://ge.apache.org/scans/tests?search.relativeStartTime=P28D=kafka=Europe/Berlin
> and general build failures:
> https://ge.apache.org/scans/failures?search.relativeStartTime=P28D=kafka=Europe/Berlin
>
> A
Hi Kirk
I have been using this new tool to analyze the trends of test
failures:
https://ge.apache.org/scans/tests?search.relativeStartTime=P28D=kafka=Europe/Berlin
and general build failures:
https://ge.apache.org/scans/failures?search.relativeStartTime=P28D=kafka=Europe/Berlin
About
Hi all!
I’ve noticed that we’re back in the state where it’s tough to get a clean PR
Jenkins test run. Spot checking the top ~10 pull request runs show this doesn’t
appear to be an issue with just my PRs :P
I know we have some chronic flaky tests, but I’ve seen at least two other
classes of
Hi Divij,
I’m hitting something similar in my pull request test run
(https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka-pr/detail/PR-13990/26/pipeline/10):
> Task :clients:testClasses
Unexpected exception thrown.
org.gradle.internal.remote.internal.MessageIOException: Could
Hey folks
We are having increased flaky failures for the past one day.
Mostly, streams upgrade tests (:streams:upgrade-system-tests-20:unitTest)
are failing with
org.gradle.internal.remote.internal.ConnectException: Could not
connect to server [90d54b62-a664-438e-b241-20847ead1eab port:34765,
> * ConnectorClientPolicyIntegrationTest
> > > > > > > > * ConnectorTopicsIntegrationTest
> > > > > > > > * ExactlyOnceSourceIntegrationTest
> > > > > > > > * OffsetsApiIntegrationTest
> > > > > > > > I'll star
> > I'll start investigating these failures to learn more.
> > > > > > >
> > > > > > > I also have a few older flaky test improvements that have not
> > been
> > > > > > reviewed
> > > > > > > or merged yet
t; > > > address CoordinatorTest (reappeared in the linked build)
> > > > > > * https://issues.apache.org/jira/browse/KAFKA-14345 to address
> > > > > > (Dynamic)ConnectionQuotaTest
> > > > > >
> > > > > &g
14345 to address
> > > > > (Dynamic)ConnectionQuotaTest
> > > > >
> > > > > It also appears that the flakey AuthorizerTest should be addressed
> by
> > > > > https://github.com/apache/kafka/pull/13543 which is on trunk now
> but
> > >
nQuotaTest
> > > >
> > > > It also appears that the flakey AuthorizerTest should be addressed by
> > > > https://github.com/apache/kafka/pull/13543 which is on trunk now but
> > > > wasn't
> > > > at the time of the above run.
> > >
but
> > > wasn't
> > > at the time of the above run.
> > >
> > > Thanks,
> > > Greg
> > >
> > > On Fri, Apr 14, 2023 at 10:25 AM Ismael Juma
> wrote:
> > >
> > > > Thanks Justine!
> > > >
> > > &
> > >
> > > On Fri, Apr 14, 2023 at 9:53 AM Justine Olshan
> > >
> > > wrote:
> > >
> > > > Hey Ismael -- thanks for bringing this up.
> > > > I've filed https://issues.apache.org/jira/browse/KAFKA-14904 and am
> > > > working
> > >
shan
> >
> > wrote:
> >
> > > Hey Ismael -- thanks for bringing this up.
> > > I've filed https://issues.apache.org/jira/browse/KAFKA-14904 and am
> > > working
> > > on it now.
> > >
> > > I hope the other tests get fixed soon.
>
> > Hey Ismael -- thanks for bringing this up.
> > I've filed https://issues.apache.org/jira/browse/KAFKA-14904 and am
> > working
> > on it now.
> >
> > I hope the other tests get fixed soon.
> >
> > On Fri, Apr 14, 2023 at 6:47 AM Ismael Juma wro
Apr 14, 2023 at 6:47 AM Ismael Juma wrote:
>
> > Hi team,
> >
> > It looks like there are a lot of test failures in the master branch. I
> > don't know which commits introduced them, but can you please check if
> > commit(s) you merged or contributed are the re
Hey Ismael -- thanks for bringing this up.
I've filed https://issues.apache.org/jira/browse/KAFKA-14904 and am working
on it now.
I hope the other tests get fixed soon.
On Fri, Apr 14, 2023 at 6:47 AM Ismael Juma wrote:
> Hi team,
>
> It looks like there are a lot of test
Hi team,
It looks like there are a lot of test failures in the master branch. I
don't know which commits introduced them, but can you please check if
commit(s) you merged or contributed are the reason and fix it asap? If it's
easy to fix the tests, let's do that - otherwise we should revert
[
https://issues.apache.org/jira/browse/KAFKA-9061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang resolved KAFKA-9061.
--
Resolution: Cannot Reproduce
> StreamStreamJoinIntegrationTest flaky test failu
Chris Pettitt created KAFKA-9061:
Summary: StreamStreamJoinIntegrationTest flaky test failures
Key: KAFKA-9061
URL: https://issues.apache.org/jira/browse/KAFKA-9061
Project: Kafka
Issue Type
Chandrasekhar created KAFKA-8711:
Summary: Kafka 2.3.0 Transient Unit Test Failures
SocketServerTest. testControlPlaneRequest
Key: KAFKA-8711
URL: https://issues.apache.org/jira/browse/KAFKA-8711
Chandrasekhar created KAFKA-8706:
Summary: Kafka 2.3.0 Unit Test Failures on Oracle Linux 7.2 - Need
help debugging framework or issue.
Key: KAFKA-8706
URL: https://issues.apache.org/jira/browse/KAFKA-8706
[
https://issues.apache.org/jira/browse/KAFKA-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang resolved KAFKA-1482.
--
Resolution: Cannot Reproduce
Fix Version/s: (was: 1.1.0)
> Transient test failu
Github user rajinisivaram closed the pull request at:
https://github.com/apache/kafka/pull/3773
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
GitHub user rajinisivaram opened a pull request:
https://github.com/apache/kafka/pull/3773
MINOR: Fix unit test failures from last commit, cherry-pick fix for SASL
principal
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
[
https://issues.apache.org/jira/browse/KAFKA-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-1482:
---
Fix Version/s: (was: 0.11.0.0)
0.11.1.0
> Transient test failu
[
https://issues.apache.org/jira/browse/KAFKA-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang updated KAFKA-1482:
-
Component/s: unit tests
> Transient test failu
[
https://issues.apache.org/jira/browse/KAFKA-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang reopened KAFKA-1482:
--
> Transient test failu
[
https://issues.apache.org/jira/browse/KAFKA-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang updated KAFKA-1482:
-
Fix Version/s: (was: 0.8.2.0)
0.10.3.0
> Transient test failu
://builds.apache.org/job/kafka-pr-jdk8-scala2.12/776/testReport/junit/kafka.admin/DeleteTopicTest/testPartitionReassignmentDuringDeleteTopic/
> Transient test failures for
> kafka.admin.DeleteTopicTest.testPartitionReassignmentDuringDelet
[
https://issues.apache.org/jira/browse/KAFKA-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang updated KAFKA-1482:
-
Summary: Transient test failures
)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{code}
was:
A couple of test cases have timing related transient test failures
[
https://issues.apache.org/jira/browse/KAFKA-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-1573:
---
Fix Version/s: (was: 0.10.1.1)
> Transient test failures on LogTest.testCorrupt
[
https://issues.apache.org/jira/browse/KAFKA-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang resolved KAFKA-1573.
--
Resolution: Not A Problem
> Transient test failures on LogTest.testCorrupt
VM and was not able to
reproduce this.
> Transient test failures on LogTest.testCorruptLog
> -
>
> Key: KAFKA-1573
> URL: https://issues.apache.org/jira/browse/KAFKA-1573
> Project: Kafk
[
https://issues.apache.org/jira/browse/KAFKA-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated KAFKA-1573:
--
Assignee: Priyank Shah
> Transient test failures on LogTest.testCorrupt
Github user asfgit closed the pull request at:
https://github.com/apache/kafka/pull/1590
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
to reproduce on
my local machine, but it always passed for me.
> Transient test failures on LogTest.testCorruptLog
> -
>
> Key: KAFKA-1573
> URL: https://issues.apache.org/jira/browse/KAFKA-1573
>
[
https://issues.apache.org/jira/browse/KAFKA-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15298901#comment-15298901
]
Gwen Shapira commented on KAFKA-1573:
-
[~guozhang] is this still failing?
> Transient test failu
[
https://issues.apache.org/jira/browse/KAFKA-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava updated KAFKA-1573:
-
Labels: transient-unit-test-failure (was: )
> Transient test failu
as part of KAFKA-3475.
> Transient test failures due to MiniKDC port allocation strategy
> ---
>
> Key: KAFKA-3453
> URL: https://issues.apache.org/jira/browse/KAFKA-3453
>
[
https://issues.apache.org/jira/browse/KAFKA-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-3453:
---
Reviewer: Gwen Shapira
> Transient test failures due to MiniKDC port allocation strat
://github.com/apache/kafka/pull/1131
> Transient test failures due to MiniKDC port allocation strategy
> ---
>
> Key: KAFKA-3453
> URL: https://issues.apache.org/jira/browse/KAFKA-3453
>
Github user ijuma closed the pull request at:
https://github.com/apache/kafka/pull/1131
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
://github.com/apache/kafka/pull/1131
KAFKA-3453; Transient test failures due to MiniKDC port allocation strategy
Temporarily copy fixed `MiniKdc` class until `MiniKdc` 2.8.0 is released.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ijuma
GitHub user ijuma opened a pull request:
https://github.com/apache/kafka/pull/1131
KAFKA-3453; Transient test failures due to MiniKDC port allocation strategy
Temporarily copy fixed `MiniKdc` class until `MiniKdc` 2.8.0 is released.
You can merge this pull request into a Git
[
https://issues.apache.org/jira/browse/KAFKA-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-3453:
---
Fix Version/s: 0.10.0.1
> Transient test failures due to MiniKDC port allocation strat
issue to
myself so that I don't forget.
> Transient test failures due to MiniKDC port allocation strategy
> ---
>
> Key: KAFKA-3453
> URL: https://issues.apache.org/jira/br
[
https://issues.apache.org/jira/browse/KAFKA-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma reassigned KAFKA-3453:
--
Assignee: Ismael Juma
> Transient test failures due to MiniKDC port allocation strat
is described
here:
https://github.com/apache/hadoop/commit/8fb70a031b323634ddc51ff6aff4f376baef68c8
> Transient test failures due to MiniKDC port allocation strategy
> ---
>
> Key: KAFKA-3453
>
Ewen Cheslack-Postava created KAFKA-3453:
Summary: Transient test failures due to MiniKDC port allocation
strategy
Key: KAFKA-3453
URL: https://issues.apache.org/jira/browse/KAFKA-3453
Github user asfgit closed the pull request at:
https://github.com/apache/kafka/pull/998
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
://github.com/apache/kafka/pull/949
> Large number of system test failures
>
>
> Key: KAFKA-3256
> URL: https://issues.apache.org/jira/browse/KAFKA-3256
> Project: Kafka
> Issue Type: Bug
resolved by pull request 949
[https://github.com/apache/kafka/pull/949]
> Large number of system test failures
>
>
> Key: KAFKA-3256
> URL: https://issues.apache.org/jira/browse/KAFKA-3256
>
ket@gmail.com>
Date: 2016-02-21T06:03:27Z
KAFKA-3256: Add print.timestamp option to console consumer. It is disabled
by default
> Large number of system test failures
>
>
> Key: KAFKA-3256
> URL: https://i
[
https://issues.apache.org/jira/browse/KAFKA-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiangjie Qin updated KAFKA-3256:
Status: Patch Available (was: Open)
> Large number of system test failu
think tear down
timeout failures are unrelated and I don't think hey actually cause any issues
([~geoffra] ?).
I'll take on upgrade and compatibility system tests if you don't mind.
> Large number of system test failures
>
>
> Key
upgrade test is testing), is that correct?
> Large number of system test failures
>
>
> Key: KAFKA-3256
> URL: https://issues.apache.org/jira/browse/KAFKA-3256
> Project: Kafka
>
compatibility test in the other two separate patches.
> Large number of system test failures
>
>
> Key: KAFKA-3256
> URL: https://issues.apache.org/jira/browse/KAFKA-3256
> Project: Kafka
>
tests. Those failures did not affect the test results but from the logs it
seems all the servers have successfully shutdown.
I agree that we can check in this patch first and fix upgrade test and producer
compatibility test in the other two separate patches.
> Large number of system test failu
and
KAFKA-3188) to add 0.8 to 0.10 and 0.9 to 0.10 upgrade tests, and test
compatibility of mix of 0.9 and 0.10 clients with 0.10 brokers. My proposal to
have a patch with current fixes, and address compatibility and upgrade test
failures as part of KAFKA-3201 and KAFKA-3188, which
failure. [~ijuma]
kicked a off a new build with better logging. It shows many broker tear down
failures. I'll take a looks at the log to see what happened.
> Large number of system test failures
>
>
> Key: KAFKA-3256
>
[
https://issues.apache.org/jira/browse/KAFKA-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15156340#comment-15156340
]
Jiangjie Qin commented on KAFKA-3256:
-
Thanks for the help, Geoff.
> Large number of system t
building kafka for
some reason.
I cleared the workspace and kicked off another run here:
https://jenkins.confluent.io/job/kafka_system_tests_branch_builder/356/console
> Large number of system test failures
>
>
> Key
ber of system test failures
>
>
> Key: KAFKA-3256
> URL: https://issues.apache.org/jira/browse/KAFKA-3256
> Project: Kafka
> Issue Type: Bug
>Reporter: Geoff Anderson
>
system
tests again? Geoff has given you permission to Confluence jenkins and you can
run the tests on your branch.
> Large number of system test failures
>
>
> Key: KAFKA-3256
> URL: https://issues.apache.org/jira/br
:
mirror_maker_test.py, zookeeper_security_upgrade_test.py, and upgrade_test.py
all use console consumer and set message_validator=is_int. So, they all expect
console consumer to output values that are integers, and additional
"CreateTime:> breaks that.
> Large number of system te
and timestamp by default. If we want to
write/extend system tests that specifically checks for timestamps (type or
validates timestamp range), then we will use an output with a timestamp.
> Large number of system test failures
>
>
> Key
by default. If we want to
write/extend system tests that specifically checks for timestamps (type or
validates timestamp range), then we will use an output with a timestamp.
> Large number of system test failures
>
>
> Key
ber of system test failures
>
>
> Key: KAFKA-3256
> URL: https://issues.apache.org/jira/browse/KAFKA-3256
> Project: Kafka
> Issue Type: Bug
>Reporter: Geoff Anderson
>
e consumer and disable it by
default then we only need one patch, right?
> Large number of system test failures
>
>
> Key: KAFKA-3256
> URL: https://issues.apache.org/jira/browse/KAFKA-3256
> Project:
an option for console
consumer. We can have a "print.timestamp" as well and disable it by default.
> Large number of system test failures
>
>
> Key: KAFKA-3256
> URL: https://issues.apache.org/jira/brow
format change so that the system tests pass again and then discuss the best way
to handle adding it back).
> Large number of system test failures
>
>
> Key: KAFKA-3256
> URL: https://issues.apache.org/jira/br
(revert the output
format change so that the system tests pass again and then discuss the best way
to handle adding it back).
> Large number of system test failures
>
>
> Key: KAFKA-3256
> URL: https://issues.apache.
is set for
compatibility reasons.
> Large number of system test failures
>
>
> Key: KAFKA-3256
> URL: https://issues.apache.org/jira/browse/KAFKA-3256
> Project: Kafka
> Issue Type: Bug
patch for this ticket that updates both the
ConsumerConsumer output format and integration test message format.
> Large number of system test failures
>
>
> Key: KAFKA-3256
> URL: https://issues.apache.org/jira/br
What was the reason for outputting timestamp type and timestamp in
ConsoleConsumer? If it does not bring much value, I propose to just got back to
the original format of outputting key and value in ConsoleConsumer. I think
that would fix most of the tests.
> Large number
, in run_produce_consume_validate
raise e
{noformat}
I am not super familiar with those tests, so might it might take me some time
to check. It looks we have problem when starting validating consumer.
> Large number of system test failures
>
uot;, "CreateTime:1455962758003\trazz",
"CreateTime:1455962758009\tma", "CreateTime:1455962758009\ttazz"] in Kafka
ConsoleConsumer was changed to also output timestamp type and timestamp value
in addition to key/value. However, it looks connect tests e
{code}
Note that directories corresponding to individual tests are actually tarballed,
and can be unpacked with:
tar xzf INDIVIDUAL_TEST_DIRECTORY
> Large number of system test failures
>
>
> Key: KAFKA-3256
>
to this link and view the
report?
http://confluent-kafka-system-test-results.s3-us-west-2.amazonaws.com/2016-02-20--001.1455979842--apache--trunk--5caa800/report.html
> Large number of system test failures
>
>
> Key: KAFKA-3256
>
] It seems I am not able to access the test report on AWS S3. Do you
mind uploading it in this ticket?
was (Author: becket_qin):
[~hachikuji] It seems I am not be able to access the test report on AWS S3. Do
you mind uploading it in this ticket?
> Large number of system test failu
report on AWS S3. Do
you mind uploading it in this ticket?
> Large number of system test failures
>
>
> Key: KAFKA-3256
> URL: https://issues.apache.org/jira/browse/KAFKA-3256
> Project: Kafka
>
tem test failures
>
>
> Key: KAFKA-3256
> URL: https://issues.apache.org/jira/browse/KAFKA-3256
> Project: Kafka
> Issue Type: Bug
>Reporter: Geoff Anderson
>
> Conflu
[
https://issues.apache.org/jira/browse/KAFKA-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiangjie Qin reassigned KAFKA-3256:
---
Assignee: Jiangjie Qin
> Large number of system test failu
Geoff Anderson created KAFKA-3256:
-
Summary: Large number of system test failures
Key: KAFKA-3256
URL: https://issues.apache.org/jira/browse/KAFKA-3256
Project: Kafka
Issue Type: Bug
re
>Affects Versions: 0.9.1.0
>Reporter: Rajini Sivaram
>Assignee: Rajini Sivaram
> Fix For: 0.9.1.0
>
>
> Stack traces in some of the transient unit test failures indicate that
> temporary directories used for Zookeeper are being reuse
ing to transient unit test failures
> --
>
> Key: KAFKA-2718
> URL: https://issues.apache.org/jira/browse/KAFKA-2718
> Project: Kafka
> Issue Type: Sub-task
-git-pr-jdk7/1606/testReport/junit/kafka.api/SaslSslConsumerTest/testListTopics/
> Reuse of temporary directories leading to transient unit test failures
> --
>
> Key: KAFKA-2718
>
at:
https://github.com/apache/kafka/pull/613
> Reuse of temporary directories leading to transient unit test failures
> --
>
> Key: KAFKA-2718
> URL: https://issues.apache.org/jira/br
://github.com/apache/kafka/pull/613
KAFKA-2718: Add logging to investigate intermittent unit test failures
Print port and directories used by zookeeper in unit tests to figure out
which may be causing conflict.
You can merge this pull request into a Git repository by running:
$ git
[
https://issues.apache.org/jira/browse/KAFKA-2718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajini Sivaram reopened KAFKA-2718:
---
> Reuse of temporary directories leading to transient unit test failu
will submit a PR with more
logging to see if we can get more info when the failure occurs.
> Reuse of temporary directories leading to transient unit test failures
> --
>
> Key: KAFKA-2718
>
in, could you take
another look to see if it is related?
https://builds.apache.org/job/kafka-trunk-git-pr-jdk7/1543/testReport/junit/kafka.api/SaslPlaintextConsumerTest/testPauseStateNotPreservedByRebalance/
> Reuse of temporary directories leading to transient unit test failu
://github.com/apache/kafka/pull/583
> Reuse of temporary directories leading to transient unit test failures
> --
>
> Key: KAFKA-2718
> URL: https://issues.apache.org/jira/br
rectories leading to transient unit test failures
> --
>
> Key: KAFKA-2718
> URL: https://issues.apache.org/jira/browse/KAFKA-2718
> Project: Kafka
> Issue Type: Sub
are run in parallel. Will
submit a new PR.
> Reuse of temporary directories leading to transient unit test failures
> --
>
> Key: KAFKA-2718
> URL: https://issues.apache.org/jira/br
1 - 100 of 146 matches
Mail list logo
