Bug 972566

Summary:	dmesg errors with no content
Product:	[Retired] Beaker	Reporter:	Marian Ganisin <mganisin>
Component:	beah	Assignee:	beaker-dev-list
Status:	CLOSED DUPLICATE	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.12	CC:	aigao, asaha, azelinka, dcallagh, llim, qwan, rmancy
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-02-19 22:51:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Marian Ganisin 2013-06-10 05:59:33 UTC

Description of problem:

Recently I saw quite significant amount of ./dmesg errors in several tests which seems to be part of harness as I am not aware of code catching in in test itself. Unfortunately the test log of ./dmesg does not contain usefull information. It contains just this:

Checking dmesg for specific failures!
------------[ cut here ]------------
End of log.

Looking at the dmesg itself reveals the call trace.

Version-Release number of selected component (if applicable):
Version - 0.12.1

Actual results:
No call trace in the test log of ./dmesg

Expected results:
Call trace reported

Comment 5 Dan Callaghan 2014-02-19 22:51:01 UTC


*** This bug has been marked as a duplicate of bug 1026670 ***