[ 
https://issues.apache.org/jira/browse/CASSANDRA-17594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17531887#comment-17531887
 ] 

David Capwell edited comment on CASSANDRA-17594 at 5/4/22 6:40 PM:
-------------------------------------------------------------------

fun, if I revert conftest.py I see it logs that there were errors in the log, 
but the test is marked as success... so by fixing conftest.py I now cause the 
tests to fail !

yay?

{code}
18:39:33,839 repair_tests.repair_test DEBUG Killed node3, now waiting repair to 
finish
PASSED                                                                          
                                                                                
                                         [100%]
----------------------------------------------------------------------------------------------
 live log teardown 
-----------------------------------------------------------------------------------------------
18:39:33,859 conftest ERROR Unexpected error in node1 log, error:
'ERROR [Repair#1:1] 2022-05-04 18:39:20,930 JVMStabilityInspector.java:68 - 
Exception in thread 
Thread[Repair#1:1,5,Repair#1]\norg.apache.cassandra.repair.SomeRepairFailedException:
 null'


-------------------------------------------------------------------------- 
generated xml file: /parallel-ci/output/pytest_result.xml 
---------------------------------------------------------------------------
==========================================================================================
 1 passed in 87.70 seconds 
===========================================================================================
bash-4.2$
{code}


was (Author: dcapwell):
fun, if I revert conftest.py I see it logs that there were errors in the log, 
but the test is marked as success... so by fixing conftest.py I now cause the 
tests to fail !

yay?

> Fix flaky python-tests due to connection getting closed
> -------------------------------------------------------
>
>                 Key: CASSANDRA-17594
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17594
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Test/dtest/python
>            Reporter: David Capwell
>            Assignee: David Capwell
>            Priority: Normal
>             Fix For: NA
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> We log unknown exceptions at the networking level, which includes case where 
> the remote side closes the connection (such as the cases caused by shutting 
> down), depending on how quickly the instances shutdown, this could cause 
> python-dtest to fail for random tests with a message such as
> {code}
> Unexpected error found in node logs (see stdout for full details). Errors: 
> [WARN  [epollEventLoopGroup-5-9] 2022-05-03T16:47:03,800 
> ExceptionHandlers.java:134 - Unknown exception in client networking
> io.netty.channel.unix.Errors$NativeIoException: writeAddress(..) failed: 
> Connection reset by peer, WARN  [epollEventLoopGroup-5-9] 
> 2022-05-03T16:47:03,800 ExceptionHandlers.java:134 - Unknown exception in 
> client networking
> io.netty.channel.unix.Errors$NativeIoException: writeAddress(..) failed: 
> Connection reset by peer]
> {code}



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to