yahoo-eng-team team mailing list archive

[Maru Newby <marun@xxxxxxxxxx>]

This commit is almost 2 weeks old, and the unit tests appear to be
running fine in the gate.  Can you replicate the problem against HEAD?

** Changed in: quantum
       Status: New => Incomplete

** Changed in: quantum
       Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to quantum.
https://bugs.launchpad.net/bugs/1171730

Title:
  unit tests fail

Status in OpenStack Quantum (virtual network service):
  Invalid

Bug description:
  The unit tests fail since the commit
  commit 4eab424be34840e5c2c16027f796c958cf3c35c3
  Merge: de5c1e4 147038a
  Author: Jenkins <jenkins@xxxxxxxxxxxxxxxxxxxx>
  Date:   Wed Apr 10 21:38:13 2013 +0000

      Merge "Parallelize quantum unit testing:"
  https://github.com/openstack/quantum/commit/4eab424be34840e5c2c16027f796c958cf3c35c3


  stack@host1:/opt/stack/quantum$ tox -e py27 -v -- -v
  using tox.ini: /opt/stack/quantum/tox.ini
  using tox-1.4.3 from /usr/local/lib/python2.7/dist-packages/tox/__init__.pyc
  GLOB sdist-make: /opt/stack/quantum/setup.py
    /opt/stack/quantum$ /usr/bin/python /opt/stack/quantum/setup.py sdist --formats=zip --dist-dir /opt/stack/quantum/.tox/dist >/opt/stack/quantum/.tox/log/tox-0.log
  py27 reusing: /opt/stack/quantum/.tox/py27
  py27 inst-nodeps: /opt/stack/quantum/.tox/dist/quantum-2013.2.a401.g11639a2.zip
    /opt/stack/quantum/.tox/py27/log$ /opt/stack/quantum/.tox/py27/bin/pip install /opt/stack/quantum/.tox/dist/quantum-2013.2.a401.g11639a2.zip -U --no-deps >/opt/stack/quantum/.tox/py27/log/py27-23.log
  py27 runtests: commands[0]
    /opt/stack/quantum$ /opt/stack/quantum/.tox/py27/bin/python tools/patch_tox_venv.py 
  py27 runtests: commands[1]
    /opt/stack/quantum$ /opt/stack/quantum/.tox/py27/bin/python setup.py testr --slowest --testr-args=-v 
  running testr
  Usage: setup.py run [options] testfilters* doubledash? testargs*

  Run the tests for a project and load them into testrepository.
      
  Configuring via .testr.conf:
  ---
  [DEFAULT]
  test_command=foo $IDOPTION
  test_id_option=--bar $IDFILE
  ---
  will cause 'testr run' to run 'foo' to execute tests, and
  'testr run --failing' will cause 'foo --bar failing.list ' to be run to
  execute tests. Shell variables are expanded in these commands on platforms
  that have a shell.

  The full list of options and variables for .testr.conf:
  * filter_tags -- a list of tags which should be used to filter test counts.
    This is useful for stripping out non-test results from the subunit stream
    such as Zope test layers. These filtered items are still considered for
    test failures.
  * test_command -- command line to run to execute tests.
  * test_id_option -- the value to substitute into test_command when specific
    test ids should be run.
  * test_id_list_default -- the value to use for $IDLIST when no specific
    test ids are being run.
  * test_list_option -- the option to use to cause the test runner to report
    on the tests it would run, rather than running them. When supplied the
    test_command should output on stdout all the test ids that would have
    been run if every other option and argument was honoured, one per line.
    This is required for parallel testing, and is substituted into $LISTOPT.
  * test_run_concurrency -- Optional call out to establish concurrency.
    Should return one line containing the number of concurrent test runner
    processes to run.
  * instance_provision -- provision one or more test run environments.
    Accepts $INSTANCE_COUNT for the number of instances desired.
  * instance_execute -- execute a test runner process in a given environment.
    Accepts $INSTANCE_ID, $FILES and $COMMAND. Paths in $FILES should be
    synchronised into the test runner environment filesystem. $COMMAND can
    be adjusted if the paths are synched with different names.
  * instance_dispose -- dispose of one or more test running environments.
    Accepts $INSTANCE_IDS.
  * $IDOPTION -- the variable to use to trigger running some specific tests.
  * $IDFILE -- A file created before the test command is run and deleted
    afterwards which contains a list of test ids, one per line. This can
    handle test ids with emedded whitespace.
  * $IDLIST -- A list of the test ids to run, separated by spaces. IDLIST
    defaults to an empty string when no test ids are known and no explicit
    default is provided. This will not handle test ids with spaces.

  See the testrepository manual for example .testr.conf files in different
  programming languages.

  setup.py: error: no such option: -v
  ERROR: InvocationError: '/opt/stack/quantum/.tox/py27/bin/python setup.py testr --slowest --testr-args=-v'
  ____________________________________________________________________________________________________________ summary ____________________________________________________________________________________________________________
  ERROR:   py27: commands failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/quantum/+bug/1171730/+subscriptions