1. 30 Nov, 2020 1 commit
  2. 26 Nov, 2020 1 commit
  3. 20 Nov, 2020 1 commit
    • Laszlo Agocs's avatar
      Fix random number generation · 13bb5aa8
      Laszlo Agocs authored
      The table was filled with the same one number, leading to significantly
      different visual results compared to 5.15, because tests relying on
      random number generation for item positions placed all 1000 or so items
      to the exact same position in the scene.
      
      Amends 01a08c32
      
      Change-Id: I817de76b7142b68751b801ca9891d2afc7234acf
      Reviewed-by: Fabian Kosmale's avatarFabian Kosmale <fabian.kosmale@qt.io>
      13bb5aa8
  4. 30 Sep, 2020 1 commit
  5. 30 Jun, 2020 1 commit
  6. 18 Jun, 2020 1 commit
  7. 18 May, 2020 1 commit
  8. 05 May, 2020 1 commit
  9. 28 Jan, 2020 1 commit
  10. 15 Jan, 2020 1 commit
  11. 04 Oct, 2019 1 commit
  12. 25 Jun, 2019 2 commits
  13. 06 May, 2019 1 commit
  14. 21 Feb, 2019 1 commit
  15. 20 Feb, 2019 1 commit
  16. 12 Oct, 2018 1 commit
  17. 19 Jul, 2018 1 commit
  18. 13 Jul, 2018 1 commit
  19. 15 Jun, 2018 1 commit
  20. 18 Jan, 2018 3 commits
  21. 17 Jan, 2018 1 commit
  22. 08 Jan, 2018 2 commits
  23. 15 Nov, 2017 1 commit
    • Eskil Abrahamsen-Blomfeldt's avatar
      Try to get a better random spread for tests with static count 20k · 10c46763
      Eskil Abrahamsen-Blomfeldt authored
      Some tests, where the static count was set to 20000 would collect
      all items along a diagonal line. It seems as if the reason for this
      was that QML would evaluate all Xs first and then all Ys, and since
      the static count was an exact multiple of the size of the
      pregenerated array, the multiplier for X and Y would be the same,
      so they would gather along the diagonal.
      
      By setting the size of the array we make this unlikely (tests
      with static count 20002 will still encounter the issue, but we
      have none of those.)
      
      Change-Id: I2d1df3c17f270a185e73e53d4ec9e2b56ddc799d
      Reviewed-by: Eskil Abrahamsen-Blomfeldt's avatarEskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>
      10c46763
  24. 31 Oct, 2017 1 commit
    • Eskil Abrahamsen-Blomfeldt's avatar
      Add internal random generator · ab770345
      Eskil Abrahamsen-Blomfeldt authored
      In Qt 5.10 we introduce a new QRandomGenerator which is now
      used by Math.random(), and there are signs that this is
      significantly slower than qrand() which was used before. So
      much so, that it is visible in many of the qmlbench benchmarks.
      Note that this is a theory based on local runs and analysis of
      the graphs and still needs to be proven.
      
      Regardless, the qmlbench benchmarks are not intended to be
      benchmarking Math.random(), it is just used to ensure the
      positions tested are random. To eliminate that as a
      possible cause for regressions, we instead introduce a
      simple internal random function which just cycles through
      a pregenerated array.
      
      Note that this will reduce performance for all affected
      tests on all branches of Qt, but it will hopefully reduce
      the gap between Qt 5.9.0 and Qt 5.10.
      
      Task-number: QTBUG-63922
      Change-Id: Ib19c11323f38b23f9705e0d77a52a8a0f1157ac3
      Reviewed-by: default avatarThiago Macieira <thiago.macieira@intel.com>
      ab770345
  25. 23 Oct, 2017 1 commit
  26. 10 Jul, 2017 1 commit
  27. 29 Jun, 2017 1 commit
  28. 28 Jun, 2017 1 commit
  29. 25 May, 2017 3 commits
  30. 19 May, 2017 1 commit
  31. 17 May, 2017 1 commit
  32. 15 May, 2017 2 commits
  33. 11 May, 2017 1 commit