impala-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Amos Bird <>
Subject Re: Bootstrapping a impala dev failed on fresh installed Ubuntu 14.04
Date Wed, 02 Nov 2016 13:02:24 GMT

Ah, re-login does the trick. Thanks for you help ;).

However, the e2e test yells so many errors.

1) the name of the directory containing the error log is strange. It
 literaly looks like this:

2) the commit I tested is 7fc31b534d4c5cb118c559e16556a6c1ae6ca7fc

3) when executing tests/, it gave:
Traceback (most recent call last):
  File "./tests/", line 94, in <module>
  File "./tests/", line 63, in run_tests
    exit_code = pytest.main(args)
  File "/home/amos/impala/infra/python/env/local/lib/python2.7/site-packages/_pytest/",
line 32, in main
    config = _prepareconfig(args, plugins)
  File "/home/amos/impala/infra/python/env/local/lib/python2.7/site-packages/_pytest/",
line 78, in _prepareconfig
    args = shlex.split(args)
  File "/usr/lib/python2.7/", line 279, in split
    return list(lex)
  File "/usr/lib/python2.7/", line 269, in next
    token = self.get_token()
  File "/usr/lib/python2.7/", line 96, in get_token
    raw = self.read_token()
  File "/usr/lib/python2.7/", line 172, in read_token
    raise ValueError, "No closing quotation"
ValueError: No closing quotation

4) when executing "MAX_PYTEST_FAILURES=12345678 ./bin/",
be, fe tests are passed. e2e tests fail a lot. Log files are attached.

I'm refering to this


View raw message