Cookiecutter generated projects log output three times during failed tests
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
oslotest |
Expired
|
Low
|
Unassigned |
Bug Description
Cookiecutter generated projects log output three times during failed tests, after generating a new project repo with cookiecutter, and changing the generated test_cctest.py file to:
*******
from cctest.tests import base
import logging
LOG = logging.
class TestCctest(
def test_something(
*******
Running the tests with `tox -epy27` will produce:
*******
(cc)kiall@
py27 create: /tmp/cctest/
py27 installdeps: -r/tmp/
py27 develop-inst: /tmp/cctest
py27 runtests: commands[0] | python setup.py testr --slowest --testr-args=
running testr
running=
OS_STDERR_
OS_TEST_
${PYTHON:-python} -m subunit.run discover -t ./ . --list
running=
OS_STDERR_
OS_TEST_
${PYTHON:-python} -m subunit.run discover -t ./ . --load-list /tmp/tmpBhDIJ2
=======
FAIL: cctest.
tags: worker-0
-------
stderr: {{{CRITICAL [cctest.
Traceback (most recent call last):
File "cctest/
self.
File "/tmp/cctest/
raise self.failureExc
AssertionError: False is not true
Traceback (most recent call last):
_StringException: Empty attachments:
stdout
stderr: {{{CRITICAL [cctest.
Traceback (most recent call last):
File "cctest/
self.
File "/tmp/cctest/
raise self.failureExc
AssertionError: False is not true
Traceback (most recent call last):
_StringException: Empty attachments:
stdout
stderr: {{{CRITICAL [cctest.
Traceback (most recent call last):
File "cctest/
self.
File "/tmp/cctest/
raise self.failureExc
AssertionError: False is not true
Ran 1 tests in 0.002s
FAILED (id=0, failures=1)
error: testr failed (1)
ERROR: InvocationError: '/tmp/cctest/
_______
ERROR: py27: commands failed
*******
Test file: http://
Output: http://
Changed in oslotest: | |
status: | New → Confirmed |
importance: | Undecided → Low |
I wonder if this is an oslotest problem, a testr problem, or an issue with our cookiecutter template.
Is it still happening?