Skip to content

Conversation

@wsliliang
Copy link
Contributor

fix #14809

@heliang666s
Copy link
Member

Thank you for your first contribution! Now the CI error is due to something wrong with the community upgrading the Zookeeper version, which has now been fixed, and you can start a new commit and run the CI test again.

@heliang666s
Copy link
Member

LGTM

@wsliliang
Copy link
Contributor Author

@heliang666s hi, thanks for your review, but I have nothing to commit any more, is it necessory to run the CI test again? if it is , how can I run it again without a new commit?

@heliang666s
Copy link
Member

you can try Merge branch '3.3' into ‘3.3’ or push an empty commit. @wsliliang

@wsliliang
Copy link
Contributor Author

@heliang666s thank you I tried but CI test still not success

@heliang666s
Copy link
Member

Judging from the error logs, this may be because there are other PRs running CI tests as well, which is causing the port to be occupied. You can wait a little longer and try again. @wsliliang

@AlbumenJ AlbumenJ merged commit dd1485a into apache:3.3 Oct 22, 2024
14 checks passed
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.

Spelling typo "Excepted context" in file "MetadataServiceNameMapping.java"

3 participants