#361: improve pretty log output for anaconda tests
--------------------+-------------------------------------------------------
Reporter: jlaska | Owner:
Type: task | Status: new
Priority: minor | Milestone: Finger Food
Component: tests | Resolution:
Keywords: |
--------------------+-------------------------------------------------------
Comment (by jlaska):
For the compose_tree test, what I'd probably want to see is the
'''true'''
result. For example, the test run linked above actually failed due to a
traceback (which is a valid bug). I'm not sure why that information isn't
in the log at all. The test script may not be properly capturing and
returning this failure from mock.
{{{
DEBUG util.py:250: Traceback (most recent call last):
DEBUG util.py:250: File "/usr/bin/pungi", line 222, in <module>
DEBUG util.py:250: main()
DEBUG util.py:250: File "/usr/bin/pungi", line 120, in main
DEBUG util.py:250: mypungi.doCreaterepo()
DEBUG util.py:250: File "/usr/lib/python2.7/site-
packages/pypungi/__init__.py", line 807, in doCreaterepo
DEBUG util.py:250: self._makeMetadata(self.topdir, cachedir,
compsfile, repoview=True, repoviewtitle=repoviewtitle)
DEBUG util.py:250: File "/usr/lib/python2.7/site-
packages/pypungi/__init__.py", line 764, in _makeMetadata
DEBUG util.py:250: repomatic.doPkgMetadata()
DEBUG util.py:250: File "/usr/lib/python2.7/site-
packages/createrepo/__init__.py", line 383, in doPkgMetadata
DEBUG util.py:250: self._setup_old_metadata_lookup()
DEBUG util.py:250: File "/usr/lib/python2.7/site-
packages/createrepo/__init__.py", line 369, in _setup_old_metadata_lookup
DEBUG util.py:250: self.oldData =
readMetadata.MetadataIndex(old_repo_path, opts)
DEBUG util.py:250: File "/usr/lib/python2.7/site-
packages/createrepo/readMetadata.py", line 57, in __init__
DEBUG util.py:250: self.scan()
DEBUG util.py:250: File "/usr/lib/python2.7/site-
packages/createrepo/readMetadata.py", line 64, in scan
DEBUG util.py:250: self._repo.sack.populate(self._repo, 'all', None,
False)
DEBUG util.py:250: File "/usr/lib/python2.7/site-
packages/yum/yumRepo.py", line 164, in populate
DEBUG util.py:250: if self._check_db_version(repo, mydbtype):
DEBUG util.py:250: File "/usr/lib/python2.7/site-
packages/yum/yumRepo.py", line 222, in _check_db_version
DEBUG util.py:250: return repo._check_db_version(mdtype)
DEBUG util.py:250: File "/usr/lib/python2.7/site-
packages/yum/yumRepo.py", line 1264, in _check_db_version
DEBUG util.py:250: repoXML = self.repoXML
DEBUG util.py:250: File "/usr/lib/python2.7/site-
packages/yum/yumRepo.py", line 1463, in <lambda>
DEBUG util.py:250: repoXML = property(fget=lambda self:
self._getRepoXML(),
DEBUG util.py:250: File "/usr/lib/python2.7/site-
packages/yum/yumRepo.py", line 1459, in _getRepoXML
DEBUG util.py:250: raise Errors.RepoError, msg
DEBUG util.py:250: yum.Errors.RepoError: Cannot retrieve repository
metadata (repomd.xml) for repository: garbageid. Please verify its path
and try again
}}}
As for the '''Summary''', I think all we need to know is whether
the
images were built successfully.
For '''Details''', I hesitate to suggest adding the *full* test
script
output ... but that might be an option.
--
Ticket URL: <
https://fedorahosted.org/autoqa/ticket/361#comment:3>
AutoQA <
http://autoqa.fedorahosted.org>
Automated QA project