Actions
action #19302
closedNeedle match may work on outdated screen contents
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Regressions/Crashes
Target version:
-
Start date:
2017-05-22
Due date:
% Done:
100%
Estimated time:
Description
The backend uses the whole frame similarity to determine if the screen has been updated:
https://github.com/os-autoinst/os-autoinst/blob/master/backend/baseclass.pm#L366
$sim = $lastscreenshot->similarity($image) if $lastscreenshot;
$watch->lap("similarity");
# we have two different similarity levels - one (slightly higher value, based
# t/data/user-settings-*) to determine if it's worth it to recheck needles
# and one (slightly lower as less significant) determining if we write the frame
# into the video
if ($sim <= 54) {
$self->last_image($image);
}
, i.e. if the average difference is about 0.5 bit or less (similarity is in dB), the frame is treated as unchanged.
This is problematic as a small change in the needle region may not trigger an update of $self->last_image
Updated by coolo over 7 years ago
But in most cases this is a CPU saver, I don't consider it a bug. In dubio we disable this in case of no_wait
Updated by okurz over 7 years ago
- Related to action #19408: interactive mode: stopped live view shows current needle, needle editor shows old needle added
Updated by StefanBruens over 7 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
All minor screen changes are forwarded to the needle search and video decoder after some delay.
Resolved in https://github.com/os-autoinst/os-autoinst/pull/801
Actions