mirror of
https://github.com/apache/impala.git
synced 2026-01-07 09:02:19 -05:00
f8134ff133
The symptom of this bug was that we were seeing "ValueError: bad marshal data" when trying to import from tests.hs2.test_hs2 during customer cluster tests. The problem was that we were not running the custom cluster tests through the new Impala Python virtualenv. Some tests (properly running with the virtualenv) that run before the customer cluster tests had caused the generation of pyc files for tests.hs2.test_hs2. Those pyc files then appeared corrupted when executing the custom cluster tests because the default python env is running a different version than the virtualenv those pyc files were generated from in earlier tests. Change-Id: Ie9d8f90c65921247dd885804165f9b7271ea807b Reviewed-on: http://gerrit.cloudera.org:8080/618 Reviewed-by: Casey Ching <casey@cloudera.com> Tested-by: Internal Jenkins
15 lines
424 B
Plaintext
Executable File
15 lines
424 B
Plaintext
Executable File
#!/usr/bin/env impala-python
|
|
# EASY-INSTALL-ENTRY-SCRIPT: 'pytest==2.7.2','console_scripts','py.test'
|
|
|
|
# This was copied straight from py.test, the only modification is to use impala-python
|
|
# instead of python above
|
|
|
|
__requires__ = 'pytest==2.7.2'
|
|
import sys
|
|
from pkg_resources import load_entry_point
|
|
|
|
if __name__ == '__main__':
|
|
sys.exit(
|
|
load_entry_point('pytest==2.7.2', 'console_scripts', 'py.test')()
|
|
)
|