cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andres de la Peña (Jira) <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-16852) testsome fails in the CircleCI multiplexer because the class JStackJUnitTask can't be found
Date Mon, 16 Aug 2021 17:04:00 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-16852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andres de la Peña updated CASSANDRA-16852:
------------------------------------------
          Fix Version/s:     (was: 3.11.x)
                             (was: 3.0.x)
                         3.11.12
                         3.0.26
          Since Version: 3.0.25
    Source Control Link: https://github.com/apache/cassandra/commit/07706662104fd7d471379a5ba1155c7e4fb71618
             Resolution: Fixed
                 Status: Resolved  (was: Ready to Commit)

> 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.0.26, 3.11.12
>
>
> 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message