Bug 1565853

Summary:	Profile the server/lab controller/common during a test run
Product:	[Retired] Beaker	Reporter:	Roman Joost <rjoost>
Component:	tests	Assignee:	beaker-dev-list
Status:	CLOSED WONTFIX	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	25
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-21 14:12:27 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:
Bug Depends On:
Bug Blocks:	1550312

Description Roman Joost 2018-04-10 23:18:35 UTC

Description of problem:

I would like to gather some profiling data after a full integration test run to help figuring out what is happening in Bug 1550312

We've added code to run coverage analysis, but the tests if the analysis was enabled never succeeded. In a similar fashion however we could enable profiling. Note though, I'm not advising to integrate profiling in the Jenkins runs. I think it's enough to hack up the sources once to get one run and perhaps shelve the changes in a patch on gerrit.