https://bugzilla.suse.com/show_bug.cgi?id=1204695 https://bugzilla.suse.com/show_bug.cgi?id=1204695#c1 Martin Doucha <martin.doucha@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.doucha@suse.com --- Comment #1 from Martin Doucha <martin.doucha@suse.com> --- The test was recently rewritten but it appears that it found a kernel bug. I've modified the test to print the wrong values returned by setitimer() in the third parameter and tried a few experiments with different timer values. The experiment works like this: new_timer = old_timer = {0}; new_timer.it_value.tv_usec = 9234; setitimer(type, &new_timer, NULL); new_timer.it_value.tv_usec = 10345; old_timer.it_value.tv_usec = 18456; setitimer(type, &new_timer, &old_timer); Here we check that old_timer.it_value.tv_usec < 18456 and fail because the kernel sets it to 19234. I've tried multiple value combinations and the kernel always set old_timer to 10000us more than it should be when the timer type is ITIMER_VIRTUAL or ITIMER_PROF. ITIMER_REAL appears to work correctly. The cloned job with modified test is here: https://openqa.opensuse.org/tests/2846894#step/setitimer01/8 -- You are receiving this mail because: You are on the CC list for the bug.