gabriel-tincu commented on pull request #979:
URL: https://github.com/apache/avro/pull/979#issuecomment-736323751


   > Hello! I've definitely confirmed that the build on master is failing _in 
addition to_ the maven central connectivity issues! I'm looking at this and 
raised one more issue: https://issues.apache.org/jira/browse/AVRO-2994
   > 
   > You will not get a green build on Travis until that's fixed :/
   > 
   > In the meantime, I manually patched the docker image locally and tried a 
local build x . It looks like it's failing in python 3.5 because of the 
f-string syntax !
   > 
   > ```
   > ======================================================================
   > ERROR: avro.test.test_compatibility (unittest.loader._FailedTest)
   > ----------------------------------------------------------------------
   > ImportError: Failed to import test module: avro.test.test_compatibility
   > Traceback (most recent call last):
   >   File "/usr/lib/python3.5/unittest/loader.py", line 428, in 
_find_test_path
   >     module = self._get_module_from_name(name)
   >   File "/usr/lib/python3.5/unittest/loader.py", line 369, in 
_get_module_from_name
   >     __import__(name)
   >   File "/home/rskraba/avro/lang/py/avro/test/test_compatibility.py", line 
565
   >     assert location in result.locations, f"expected {location}, found 
{result.location}"
   >                                                                            
            ^
   > SyntaxError: invalid syntax
   > ```
   > 
   > Python 3.5 reached end-of-life fairly recently if I remember correctly, 
but we're still supporting it.
   
   @RyanSkraba Sorry about that, I missed that particular reference to a stale 
class member. For some reason (probably because the test passes) that did not 
blow up locally 


----------------------------------------------------------------
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.

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


Reply via email to