Hi there,
I've just executed full integration tests run with the following result (patched
develop
branch):
Ran 1345 tests in 6731.735s
FAILED (SKIP=3, errors=70, failures=55)
real 112m14.756s
user 101m11.856s
sys 7m42.248s
Quite some errors then. Much more than I expected :). Looking at the results I have mixed
feelings.
Some selenium tests were failing (almost all in my case). When I ran the same test alone
it passed with no problems.
To get more data I ran the suite with "-sv" switch. Looking at the output there
are some
things that I'm not sure are errors or not.
For instance:
bkr.server.mail: ERROR: Exception thrown when trying to send mail
[...]
error: [Errno 111] Connection refused
bkr.server.tests.data_setup: DEBUG: Marked R:706 as complete with result Pass
or:
FAIL: test_all_tables_use_innodb (bkr.inttest.server.test_model.SchemaSanityTest)
----------------------------------------------------------------------
Traceback (most recent call last):
File
"/root/beaker-private/IntegrationTests/src/bkr/inttest/server/test_model.py",
line
55, in test_all_tables_use_innodb
table), 'InnoDB')
AssertionError: u'MyISAM' != 'InnoDB'
I've not created any new tables there (only added columns to existing tables). So how
can
this happen?
So the main question here is, are all the tests expected to pass on the develop branch? Or
what are the usual results I can compare my patches to? Are there any other requirements
besides the deps of integration tests RPM and
https://beaker-project.org/dev/guide/writing-a-patch.html#testing-your-pa...
Thank you,
Jaroslav.
PS: are the results saved somewhere or is stdout the only option? "--debug-log"
looks more
like the framework debugging than the actual tests' debug output...