Public bug reported:
on slow devices with real time timers we can get stuck handling timer
signals and never get around to the main loop that exits. ALso, SIGALRM
alarm and setitimer share the same alarm, so we never get the
termination alarm and the test never exits.
A workaround is to check for overrun in the timer handler.
** Affects: stress-ng (Ubuntu)
Importance: High
Assignee: Colin Ian King (colin-king)
Status: In Progress
** Changed in: stress-ng (Ubuntu)
Status: New => In Progress
** Changed in: stress-ng (Ubuntu)
Importance: Undecided => Medium
** Changed in: stress-ng (Ubuntu)
Importance: Medium => High
** 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/1494751
Title:
stress-ng timer/itimer race on slow devices
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1494751/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
