[
https://issues.apache.org/jira/browse/CASSANDRA-17386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17493408#comment-17493408
]
Aleksei Zotov edited comment on CASSANDRA-17386 at 2/16/22, 6:33 PM:
---------------------------------------------------------------------
Good point [~brandon.williams]! For 4.0 and 4.x the issue has been fixed in
[this
PR|https://github.com/apache/cassandra/commit/bf9a1d487b9ba469e8d740cf7d1cd419535a7e79#diff-4f28d77309cd96fadc18b2e74fb7a0c2c040ec6e68e551e1198eb2361c8a56a7R56].
I additionally checked 3.0 and looks like it has the same issue, however, it is
not being reported.
Here are the details:
[https://ci-cassandra.apache.org/view/Cassandra%203.0/job/Cassandra-3.0/248/consoleFull]
(latest 3.0):
{code:java}
14:42:08 Starting building: Cassandra-3.0-cqlsh-tests #305
{code}
and in
[https://ci-cassandra.apache.org/job/Cassandra-3.0-cqlsh-tests/305/#showFailuresLink]
there are _TestCqlshOutput_ failures. Any idea why these failures are not
being reported as failures at
[https://ci-cassandra.apache.org/view/Cassandra%203.0/job/Cassandra-3.0/248/#showFailuresLink]?
I was able to reproduce the issue for 3.0 locally. Hence I ported the same fix
to 3.0 branch, tested locally and triggered CI.
||Item||Link||
|PR 3.11|[https://github.com/apache/cassandra/pull/1450]|
|CI
3.11|[https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1429/]
(looks good)|
|PR 3.0|[https://github.com/apache/cassandra/pull/1451/]|
|CI
3.0|[https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1431/]
(running now)|
was (Author: azotcsit):
Good point [~brandon.williams]! For 4.0 and 4.x the issue has been fixed in
[this
PR|https://github.com/apache/cassandra/commit/bf9a1d487b9ba469e8d740cf7d1cd419535a7e79#diff-4f28d77309cd96fadc18b2e74fb7a0c2c040ec6e68e551e1198eb2361c8a56a7R56].
I additionally checked 3.0 and looks like it has the same issue, however, it is
not being reported.
Here are the details:
[https://ci-cassandra.apache.org/view/Cassandra%203.0/job/Cassandra-3.0/248/consoleFull]
(latest 3.0):
{code:java}
14:42:08 Starting building: Cassandra-3.0-cqlsh-tests #305
{code}
and in
[https://ci-cassandra.apache.org/job/Cassandra-3.0-cqlsh-tests/305/#showFailuresLink]
there are _TestCqlshOutput_ failures. Any idea why these failures are not
being reported as failures at
[https://ci-cassandra.apache.org/view/Cassandra%203.0/job/Cassandra-3.0/248/#showFailuresLink]?
I was able to reproduce the issue for 3.0 locally. Hence I ported the same fix
to 3.0 branch, tested locally and triggered CI.
||Item||Link||
|PR 3.11|[https://github.com/apache/cassandra/pull/1450]|
|CI
3.11|[https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1429/]
(looks good)|
|PR 3.0|[https://github.com/apache/cassandra/pull/1451/]|
|CI
3.0|[https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1431/]
(running now)|
> Test failure: TestCqlshOutput failing tests
> --------------------------------------------
>
> Key: CASSANDRA-17386
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17386
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
> Reporter: Ekaterina Dimitrova
> Assignee: Aleksei Zotov
> Priority: Normal
> Fix For: 3.11.x
>
>
> The following TestCqlshOutput tests are failing consistently on 3.11 and as
> far as Butler goes, since the very beginning it started collecting data so I
> am not able to say at this point what exactly broke them:
> Test_static_cf_output, test_boolean_output, test_count_output,
> test_string_output_ascii, test_null_output, test_columness_key_output,
> test_numeric_output
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
