You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ekaterina Dimitrova (Jira)" <ji...@apache.org> on 2021/08/12 21:50:00 UTC
[jira] [Updated] (CASSANDRA-16852) testsome fails in the CircleCI
multiplexer because the class JStackJUnitTask can't be found
[ https://issues.apache.org/jira/browse/CASSANDRA-16852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ekaterina Dimitrova updated CASSANDRA-16852:
--------------------------------------------
Description:
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 route 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.
was:
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 route 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.
> 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
> Reporter: Ekaterina Dimitrova
> Priority: Normal
>
> 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 route 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org