Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-73116

tst_QString::localeAwareCompare fails (dev)

    XMLWordPrintable

Details

    • Linux/X11
    • 76dfda1ad12cc42cdd832aed1edbe5f76b0cbb2d (qt/qtbase/5.12)

    Description

      See https://codereview.qt-project.org/#/c/250098/ 

      agent:2019/01/17 13:06:40 build.go:192: FAIL!  : tst_QString::localeAwareCompare(normalize1) 'testres == 0' returned FALSE. ()
 agent:2019/01/17 13:06:40 build.go:192:    Loc: [tst_qstring.cpp(5654)]
agent:2019/01/17 13:06:40 build.go:192: FAIL!  : tst_QString::localeAwareCompare(normalize2) 'testres == 0' returned FALSE. ()
 agent:2019/01/17 13:06:40 build.go:192:    Loc: [tst_qstring.cpp(5654)]
 agent:2019/01/17 13:06:40 build.go:192: FAIL!  : tst_QString::localeAwareCompare(normalize3) 'testres == 0' returned FALSE. ()
 agent:2019/01/17 13:06:40 build.go:192:    Loc: [tst_qstring.cpp(5654)]
agent:2019/01/17 13:06:40 build.go:192: FAIL!  : tst_QString::localeAwareCompare(normalize4) 'testres == 0' returned FALSE. ()
agent:2019/01/17 13:06:40 build.go:192:    Loc: [tst_qstring.cpp(5654)]
agent:2019/01/17 13:06:40 build.go:192: FAIL!  : tst_QString::localeAwareCompare(normalize5) 'testres == 0' returned FALSE. ()
agent:2019/01/17 13:06:40 build.go:192:    Loc: [tst_qstring.cpp(5654)]
agent:2019/01/17 13:06:40 build.go:192: FAIL!  : tst_QString::localeAwareCompare(normalize6) 'testres == 0' returned FALSE. ()
agent:2019/01/17 13:06:40 build.go:192:    Loc: [tst_qstring.cpp(5654)]
agent:2019/01/17 13:06:40 build.go:192: FAIL!  : tst_QString::localeAwareCompare(normalize7) 'testres == 0' returned FALSE. ()

      Attachments

        Issue Links

          resulted from

          Bug - A problem which impairs or prevents the functions of the product. QTQAINFRA-1631 When re-running flaky tests with logging enabled, tests can be killed due to too many messages

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Activity

            People

              Eddy Edward Welbourne
              kleint Friedemann Kleint
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: