[
https://issues.apache.org/jira/browse/CASSANDRA-16852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17398664#comment-17398664
]
Andres de la Peña commented on CASSANDRA-16852:
-----------------------------------------------
It seems we can't easily add {{build-test}} to {{jar}}, since it would produce
a circular dependency. Instead, I have simply added {{build-test}} as target of
the ant command in the {{build}} CircleCI job:
||PR||CI||
|[3.0|https://github.com/apache/cassandra/pull/1138]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/776/workflows/466c5fec-2fcf-4282-bd51-4320bda6a680]|
|[3.11|https://github.com/apache/cassandra/pull/1139]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/775/workflows/f1e4e4ae-8819-42eb-8027-4b4d23f2a780]|
That seem enough to get the multiplexer back into shape. Note that the failure
in {{j8_repeated_utest}} for 3.0 is a timeout not related to our build problem.
By the way, independently to this fix we might at some point consider using
{{-Dno-build-test=true}} with other test jobs to save some resources, even if
it doesn't have as much impact as in the multiplexer.
> testsome fails in the CircleCI multiplexer because the class JStackJUnitTask
> can't be found
> -------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-16852
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16852
> Project: Cassandra
> Issue Type: Bug
> Components: CI
> Reporter: Ekaterina Dimitrova
> Assignee: Andres de la Peña
> Priority: Normal
> Fix For: 3.11.x
>
>
> As [~adelapena] explained on
> [CASSANDRA-16827|https://issues.apache.org/jira/browse/CASSANDRA-16827?focusedCommentId=17398060&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17398060],
> the problem might be in the flag _-Dno-build-test=true_ that the multiplexer
> uses to not run _build-test_ in every iteration, relying on that this has
> already been done by the build task. This is a performance optimisation that
> can be especially effective in fast tests.
> It would be ideal to have the initial multiplexer behavior restored, but we
> can always run _ant build-test_ at the beginning of every multiplexer runner
> while still not running it on every iteration. This seems enough to keep the
> multiplexer working but it requires some extra builds and therefore higher
> costs.
> The goal of this ticket is to find the root of this failure and fix the
> multiplexer either by restoring its initial flow or adding _ant build-test_
> at the beginning of every multiplexer runner, if there is no more effective
> solution.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
