Ahmet Altay created BEAM-1044:
---------------------------------

             Summary: tests run before install fails
                 Key: BEAM-1044
                 URL: https://issues.apache.org/jira/browse/BEAM-1044
             Project: Beam
          Issue Type: Bug
          Components: sdk-py
            Reporter: Ahmet Altay
            Assignee: Vikas Kedigehalli


`python setup.py test` fails for datastore tests when run in a new virtual 
environment. Running `python setup.py install` fixes the problem but that 
should not be necessary. Stack for one of the failing tests:

======================================================================
ERROR: Failure: ImportError (cannot import name descriptor)
----------------------------------------------------------------------
Traceback (most recent call last):
  File 
"/usr/local/google/home/altay/Desktop/beam/temp/incubator-beam/sdks/python/.eggs/nose-1.3.7-py2.7.egg/nose/loader.py",
 line 418, in loadTestsFromName
    addr.filename, addr.module)
  File 
"/usr/local/google/home/altay/Desktop/beam/temp/incubator-beam/sdks/python/.eggs/nose-1.3.7-py2.7.egg/nose/importer.py",
 line 47, in importFromPath
    return self.importFromDir(dir_path, fqname)
  File 
"/usr/local/google/home/altay/Desktop/beam/temp/incubator-beam/sdks/python/.eggs/nose-1.3.7-py2.7.egg/nose/importer.py",
 line 94, in importFromDir
    mod = load_module(part_fqname, fh, filename, desc)
  File 
"/usr/local/google/home/altay/Desktop/beam/temp/incubator-beam/sdks/python/apache_beam/io/datastore/v1/query_splitter_test.py",
 line 25, in <module>
    from apache_beam.io.datastore.v1 import fake_datastore
  File 
"/usr/local/google/home/altay/Desktop/beam/temp/incubator-beam/sdks/python/apache_beam/io/datastore/v1/fake_datastore.py",
 line 21, in <module>
    from google.datastore.v1 import datastore_pb2
  File "build/bdist.linux-x86_64/egg/google/datastore/v1/datastore_pb2.py", 
line 6, in <module>
ImportError: cannot import name descriptor





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to