Bug 1565853 - Profile the server/lab controller/common during a test run
Summary: Profile the server/lab controller/common during a test run
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Beaker
Classification: Community
Component: tests
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks: 1550312
TreeView+ depends on / blocked
 
Reported: 2018-04-10 23:18 UTC by Roman Joost
Modified: 2020-10-21 14:13 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-21 14:12:27 UTC


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.