Uploaded image for project: 'Qt Quality Assurance Infrastructure'
  1. Qt Quality Assurance Infrastructure
  2. QTQAINFRA-6145

Window size is not expected in Qt3D tst_PickBoundingVolumeJob

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • P1: Critical
    • None
    • 5.15
    • None
    • Windows
    • dac2afc9c (tqtc/lts-5.15), 4e5d1e864 (tqtc/lts-5.15), ad0b5aa79 (tqtc/lts-5.15)

    Description

      There are consistent test fails when trying to integrate a nodejs update:

      538397: Update Nodejs on windows to 20.7 | https://codereview.qt-project.org/c/qt/tqtc-qt5/+/538397

      Fails happen in a module that does not use nodejs. 

      This change activates Coin to build a new provision VM for Windows 7 after 6 month break. In this new provision build, tst_PickBoundingVolumeJob test in Qt3D consistently fails with tests related to window size:

      Coin run:

      https://ci-files01-hki.ci.qt.io:8081/coin/integration/qt/tqtc-qt5/tasks/1707721221

      Qt3D Windows 7 test logs:

      FAIL!  : tst_PickBoundingVolumeJob::viewportCameraAreaGather() Compared values are not the same
          Actual   (window->size()) : QSize(600x582)
          Expected (QSize(600, 600)): QSize(600x600)

      This might be related to the new OpenNebula affecting display settings similar to ticket QTQAINFRA-5987

      Likely solution is to add/modify resolution settings for Windows 7 in Qt 5.15 like in the related ticket.

      Attachments

        Issue Links

          For Gerrit Dashboard: QTQAINFRA-6145
          # Subject Branch Project Status CR V

          Activity

            People

              eltoivol Elias Toivola
              eltoivol Elias Toivola
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:

                Gerrit Reviews

                  There are no open Gerrit changes