Skip to content

Conversation

@kaori-seasons
Copy link

Related to issue-1514

Contribution Checklist

  • Make sure that the pull request corresponds to a GitHub issue. Exceptions are made for typos in JavaDoc or documentation files, which need no issue.

  • Name the pull request in the format "[component] Title of the pull request", where [component] should be replaced by the name of the component being changed. Typically, this corresponds to the component label assigned to the issue (e.g., [kv], [log], [client], [flink]). Skip [component] if you are unsure about which is the best component.

  • Fill out the template below to describe the changes contributed by the pull request. That will give reviewers the context they need to do the review.

  • Make sure that the change passes the automated tests, i.e., mvn clean verify passes.

  • Each pull request should address only one issue, not mix up code from multiple issues.

(The sections below can be removed for hotfixes or typos)
-->

Purpose

Linked issue: close #xxx

Brief change log

Tests

API and Format

Documentation

@kaori-seasons kaori-seasons changed the title [test] add e2e test [test] add classloader e2e test Oct 23, 2025
@kaori-seasons kaori-seasons changed the title [test] add classloader e2e test [test] add e2e test Nov 11, 2025
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.

1 participant