Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-24135

Valgrind / ASAN warnings and retry-pass/retry-fail info do not go to MTR XML, XML can contain illegal symbols

    XMLWordPrintable

Details

    Description

      If MTR is started with Valgrind and test fails due to Valgrind warnings, XML file from MTR contains only ne-line message like CURRENT_TEST: main.analyze_stmt_orderby, but whole output can be visible only from Console log (so, it is not going to Jenkins report or test results DB viewer)

      Also if test case is restarted by MTR result can be retry-fail or retry-pass - such situation is not translated to XML (restarted case is mentioned only ones - there is no way to see e.g. initial failure logs if test is 'retry-pass')

      another issue: every test can be executed with different parameters, e.g.:

      innod.101_compatibility "innodb,32k" [ failed ]
      innod.101_compatibility "innodb,16k" [ passed ]
      innod.101_compatibility "innodb,8k" [ passed ]
      

      If warning, comment etc contains symbols that are illegal for XML such symbols go to CDATA filed and generated XML is malformed

      Attachments

        1. stdio (9)
          7 kB
        2. jenkins
          4 kB
        3. mtr.log
          383 kB
        4. mtr_retry_pass2.log
          385 kB
        5. mtr_big.log
          389 kB
        6. mtr_big.xml
          829 kB
        7. mtr_galera.log
          51 kB
        8. mtr_galera.xml
          56 kB
        9. mtr_apr01.log
          48 kB
        10. mtr_apr01.xml
          55 kB
        11. mtr_big_apr09.log
          387 kB
        12. mtr_big_apr09.xml
          829 kB

        Activity

          People

            anel Anel Husakovic
            tturenko Timofey Turenko
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.