458ec4cb54
Since setScaledClipRect will actually render only the necessary parts, there may be insignificant differences in rounding/anitaliasing compared to rendering the whole image first and then clipping. Hence this autotest case would always fail. But that would not happen in CI, since it tests qtbase without the qtsvg module, and then the SVG tests are skipped. (For some reason, one ran into this in wayland testing and made an exception for that, but obviously this failure has nothing to do with wayland). Work around the issue by converting the rendered images to 4 bpc format, so the differences in the least significant bits get truncated away. Fixes: QTBUG-100917 Task-number: QTBUG-81044 Pick-to: 6.4 Change-Id: I1c14e98af22d0ae22a751960b69e692c7a38399b Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io> Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io> |
||
|---|---|---|
| .. | ||
| auto | ||
| baseline | ||
| benchmarks | ||
| global | ||
| libfuzzer | ||
| manual | ||
| shared | ||
| testserver | ||
| CMakeLists.txt | ||
| README | ||
This directory contains autotests and benchmarks based on Qt Test. In order
to run the autotests reliably, you need to configure a desktop to match the
test environment that these tests are written for.
Linux X11:
* The user must be logged in to an active desktop; you can't run the
autotests without a valid DISPLAY that allows X11 connections.
* The tests are run against a KDE3 or KDE4 desktop.
* Window manager uses "click to focus", and not "focus follows mouse". Many
tests move the mouse cursor around and expect this to not affect focus
and activation.
* Disable "click to activate", i.e., when a window is opened, the window
manager should automatically activate it (give it input focus) and not
wait for the user to click the window.