[
https://issues.apache.org/jira/browse/CASSANDRA-18511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17721359#comment-17721359
]
Doug Rohrer edited comment on CASSANDRA-18511 at 5/12/23 4:40 PM:
------------------------------------------------------------------
in-jvm-dtest change:
[https://github.com/apache/cassandra-in-jvm-dtest-api/pull/34]
-Once we have a snapshot build of the API I'll post PRs for trunk/4.1/4.0/3.11-
Trunk patch:
[https://github.com/apache/cassandra/pull/2318]
4.1:
[https://github.com/apache/cassandra/pull/2328]
4.0:
[https://github.com/apache/cassandra/pull/2326]
3.11:
[https://github.com/apache/cassandra/pull/2322]
Circle CI builds (updated 2023/05/12 with new links after fixing some bugs):
Trunk:
[java8_tests|https://app.circleci.com/pipelines/github/JeetKunDoug/cassandra/69/workflows/a4387bfc-46ba-41ec-b688-db1bb7b88807]
[java11_tests|https://app.circleci.com/pipelines/github/JeetKunDoug/cassandra/69/workflows/5012b08a-8c12-4a21-ae93-2a5b0c5e8c88]
4.1:
[java8_tests|https://app.circleci.com/pipelines/github/JeetKunDoug/cassandra/66/workflows/040b9ae8-bf6b-481a-a49a-5e1eeaf1ad53]
[java11_tests|https://app.circleci.com/pipelines/github/JeetKunDoug/cassandra/66/workflows/61fbcf8a-5333-4548-a857-328ef5725507]
4.0: - both jams seeing
`[testFailingMessage[VALIDATION_REQ/parallel/true]|https://app.circleci.com/pipelines/github/JeetKunDoug/cassandra/67/workflows/a21ac700-ec75-40ec-ad50-94c03af4f5f5/jobs/1711/tests#failed-test-0]`
failing, but this is a known issue in 4.0 (see
https://issues.apache.org/jira/browse/CASSANDRA-18366)
[java8_tests|https://app.circleci.com/pipelines/github/JeetKunDoug/cassandra/67/workflows/a21ac700-ec75-40ec-ad50-94c03af4f5f5]
[java11_tests|https://app.circleci.com/pipelines/github/JeetKunDoug/cassandra/67/workflows/a1bc4c2a-3fef-48c7-a387-6005e4c55676]
3.11
[java8_tests|https://app.circleci.com/pipelines/github/JeetKunDoug/cassandra/68/workflows/74205a42-1f5b-4813-9492-d71b0879675a]
was (Author: drohrer):
in-jvm-dtest change:
[https://github.com/apache/cassandra-in-jvm-dtest-api/pull/34]
-Once we have a snapshot build of the API I'll post PRs for trunk/4.1/4.0/3.11-
Trunk patch:
[https://github.com/apache/cassandra/pull/2318]
4.1:
[https://github.com/apache/cassandra/pull/2328]
4.0:
[https://github.com/apache/cassandra/pull/2326]
3.11:
[https://github.com/apache/cassandra/pull/2322]
Circle CI builds:
Trunk:
[java8_tests|https://app.circleci.com/pipelines/github/JeetKunDoug/cassandra/61/workflows/d66e58c2-e4b8-4be5-aab6-67dca04acda1]
[java11_tests|https://app.circleci.com/pipelines/github/JeetKunDoug/cassandra/61/workflows/252cfa8b-8dd2-48ca-91e2-35a238bb9afb]
4.1:
[java8_tests|https://app.circleci.com/pipelines/github/JeetKunDoug/cassandra/62/workflows/db90513b-b962-4068-97e1-3f86204213ca]
[java11_tests|https://app.circleci.com/pipelines/github/JeetKunDoug/cassandra/62/workflows/fe854086-6762-4d1d-8a54-fe7f3bb85e5e]
4.0:
[java8_tests|https://app.circleci.com/pipelines/github/JeetKunDoug/cassandra/60/workflows/fca92510-aa38-486a-9a65-600662817991]
[java11_tests|https://app.circleci.com/pipelines/github/JeetKunDoug/cassandra/60/workflows/99ba34a6-f3df-4e4b-9dbe-cdd3a0b86a6c]
3.11
[java8_tests|https://app.circleci.com/pipelines/github/JeetKunDoug/cassandra/59/workflows/b3b5a8d7-a515-49cf-813e-2c2dd08aceb9]
(One unrelated failed in-jvm-dtest that I've seen a few times so far:
testReprepareMixedVersionWithoutReset)
> Add support for JMX in the in-jvm dtest framework
> -------------------------------------------------
>
> Key: CASSANDRA-18511
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18511
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/dtest/java
> Reporter: Doug Rohrer
> Assignee: Doug Rohrer
> Priority: Normal
> Labels: pull-request-available
> Fix For: 3.11.x, 4.0.x, 4.1.x, 5.0
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> In many cases, it would be useful to be able to enable JMX endpoints within
> the in-jvm dtest framework, including the existing JMX Getter test, which
> used to simply spin up a JMX registry and then leave it running. There are
> quite a few JMX-related functions that don’t have tests today, and some
> external usages of the in-jvm dtest framework could also benefit from
> exposing JMX like we did Native before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
