Looking at the log there is a failure message in the stressor:
stress-ng: 19:04:27.27 debug: [20634] process [833] (stress-ng-stack)
terminated on signal: 11 (Segmentation fault)
The stressor itself should not be segfaulting. The stressor forks off
child processes that can segfault (e.g. when the stack is too large) but
the parent should never segfault, hence the error is caught by the main
top-level stress-ng controlling process and reports this as a core test
failure. I believe this may be occurring because of memory pressure on
the stressor. I'll try figure out why this is occurring.
** Changed in: stress-ng (Ubuntu)
Status: New => In Progress
** Changed in: stress-ng (Ubuntu)
Importance: Undecided => Medium
** Changed in: stress-ng (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841916
Title:
stress-stack stressor terminates with segfault
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1841916/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
