absurdfarce commented on PR #1260:
URL: 
https://github.com/apache/cassandra-python-driver/pull/1260#issuecomment-3564750423

   Hey @osttra-h-jarrendal , thanks for the ping?  I'm assuming your message 
above refers to the Travis CI build?  If that's the case I don't think 
re-running the build will address the issue:
   
   ```
   ==================================== ERRORS 
====================================
   _________ ERROR at setup of LibevTimerTest.test_multi_timer_validation 
_________
   cls = <class 'tests.unit.io.test_libevreactor.LibevTimerTest'>
       @classmethod
       @noop_if_monkey_patched
       def setUpClass(cls):
           if LibevConnection is None:
   >           raise unittest.SkipTest('libev does not appear to be installed 
correctly')
   E           twisted.trial.unittest.SkipTest: libev does not appear to be 
installed correctly
   ../../../tests/unit/io/test_libevreactor.py:100: SkipTest
   ___________ ERROR at setup of LibevTimerTest.test_timer_cancellation 
___________
   cls = <class 'tests.unit.io.test_libevreactor.LibevTimerTest'>
       @classmethod
       @noop_if_monkey_patched
       def setUpClass(cls):
           if LibevConnection is None:
   >           raise unittest.SkipTest('libev does not appear to be installed 
correctly')
   E           twisted.trial.unittest.SkipTest: libev does not appear to be 
installed correctly
   ../../../tests/unit/io/test_libevreactor.py:100: SkipTest
   =============================== warnings summary 
===============================
   ```
   
   It looks like libev isn't being installed on those runners, which is a bit 
strange since we don't explicitly install it in our config.  I'll take a quick 
look and see if this is an easy fix but we'll very likely be retiring Travis 
completely now that we've moved this project to the Apache Software Foundation.
   
   We'll be setting up a new CI infra for this project there but that will take 
a bit of time to get done.  In the interim the _best_ answer is probably to run 
a test build on our old Jenkins infrastructure.  I just tried to kick that off 
for you but it looks like that's _also_ borked, apparently as a side effect of 
the move.  I'm working on getting all of that resolved but given the holidays 
it might take a while.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

Reply via email to