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

Stefan Miklosovic commented on CASSANDRA-17397:
-----------------------------------------------

They dont seem to be correlated. I have looked at few of them already and it is 
mostly about timeouts.

Not sure if it is reliable info but I built some branch on top of current trunk 
today and I got like 11 failures only, mostly notoric ones related to upgrades 

https://ci-cassandra.apache.org/job/Cassandra-devbranch/1498/#showFailuresLink

> cleanup cqlshlib unit test failures and warnings
> ------------------------------------------------
>
>                 Key: CASSANDRA-17397
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17397
>             Project: Cassandra
>          Issue Type: Bug
>          Components: CQL/Interpreter
>            Reporter: Brad Schoening
>            Assignee: Brad Schoening
>            Priority: Normal
>             Fix For: 4.1
>
>
> The cqlshlib unit tests have some regular failures and warnings.
>  # test_copyutil.py fails with too many open files when ulimit is 256
>  # cassconnect.py:39: DeprecationWarning: Legacy execution parameters
>  # sslhandling.py:42: DeprecationWarning: The SafeConfigParser class has been 
> renamed to ConfigParser 
>  # remove unused reference to nosetests.xml in Jenkinsfile
>  
> The cqlshlib test test_copyutil.py fails on MacOS with 
> *E           OSError: [Errno 24] Too many open files*
> This happens because the test does not close the file descriptors after use.  
> The default ulimit on MacOS is small, 256:
>      % ulimit -n
>      256
> The simple fix is to close the pipe after use.  Increasing ulimit nofiles 
> works also, but shouldn't be necessary.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to