Actions
action #37126
closed[functional][y] collect strace output for the installer to debug sporadic issues
Start date:
2018-07-04
Due date:
% Done:
0%
Estimated time:
Difficulty:
Description
Motivation¶
In case of sporadic issues strace would be really helpful, and if issue occurs once in 20 runs, the only chance to get information is to have automated mechanism to collect logs.
Acceptance criteria¶
AC1 There is mechanism to collect strace from SUT for the process of interest or at least installer
Suggestions¶
In case of installer we could use
strace -f -o strace.log -p `pidof ruby.ruby2.5`
To make it more generic we can pass string to find process in the variable itself and then collect created file in postfail hook in case variable is set.
Updated by okurz about 6 years ago
- Category set to Enhancement to existing tests
- Status changed from New to Rejected
- Assignee set to okurz
@riafarov, see comment above
Updated by riafarov about 6 years ago
- Follows action #35709: [functional][y][hard] Improve auto-investigation in case the yast installer gets stuck added
Actions