Hope the committer runs the tests locally. If the Jenkins tests don’t work, that is a back and forth between the team and committer. For the most part if tested locally, the Kafka team is responsible to take the PR forward from there on.
I really don’t understand the issue here On Sun, Jun 14, 2020 at 7:52 PM Michael Carter < michael.car...@instaclustr.com> wrote: > Hi all, > > I’ve submitted a patch for the first time( > https://github.com/apache/kafka/pull/8844 < > https://github.com/apache/kafka/pull/8844>), and I have a couple of > questions that I’m hoping someone can help me answer. > > I’m a little unclear what happens after that patch has been submitted. The > coding guidelines say Jenkins will run tests automatically, but I don’t see > any results anywhere. Have I misunderstood what should happen, or do I just > not know where to look? > Should I be attempting to find reviewers for the change myself, or is that > done independently of the patch submitter? > > Also, in resolving a couple of conflicts that have arisen after the patch > was first submitted, I noticed that there are now failing unit tests that > have nothing to do with my change. Is there a convention on how to deal > with these? Should it be something that I try to fix on my branch? > > Any thoughts are appreciated. > > Thanks, > Michael
