Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-15152

auster does not report correct test suite exit status

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • Lustre 2.15.0
    • None
    • None
    • 3
    • 9223372036854775807

    Description

      auster does not report correct test suite exit status

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. LU-15089 sanity-lnet test_230: expected number of tcp connections 18

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Activity

            [LU-15152] auster does not report correct test suite exit status
            pjones Peter Jones added a comment -

            Landed for 2.15

            pjones Peter Jones added a comment - Landed for 2.15
            gerrit Gerrit Updater added a comment -

            "Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/45343/
            Subject: LU-15152 tests: auster reports wrong testsuite status
            Project: fs/lustre-release
            Branch: master
            Current Patch Set:
            Commit: 1de3c3455868670c289ed1d69f57244816ea39b5

            gerrit Gerrit Updater added a comment - "Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/45343/ Subject: LU-15152 tests: auster reports wrong testsuite status Project: fs/lustre-release Branch: master Current Patch Set: Commit: 1de3c3455868670c289ed1d69f57244816ea39b5
            adilger Andreas Dilger added a comment -

            No, it looks like LU-15150 is the real source of that problem.

            adilger Andreas Dilger added a comment - No, it looks like LU-15150 is the real source of that problem.
            hornc Chris Horn added a comment - - edited

            If auster is used for maloo testing, then yes. But I just happened to notice the issue while working on LU-15150 (which prevents exit_status() from detecting the test failure)

            hornc Chris Horn added a comment - - edited If auster is used for maloo testing, then yes. But I just happened to notice the issue while working on LU-15150 (which prevents exit_status() from detecting the test failure)
            adilger Andreas Dilger added a comment -

            Presumably this is related to LU-15089 "sanity-lnet test_230: expected number of tcp connections 18" failing the subtest but not reporting an error?

            adilger Andreas Dilger added a comment - Presumably this is related to LU-15089 " sanity-lnet test_230: expected number of tcp connections 18 " failing the subtest but not reporting an error?
            gerrit Gerrit Updater added a comment -

            "Chris Horn <chris.horn@hpe.com>" uploaded a new patch: https://review.whamcloud.com/45343
            Subject: LU-15152 tests: auster reports wrong testsuite status
            Project: fs/lustre-release
            Branch: master
            Current Patch Set: 1
            Commit: d8d28c2c21d6e79f1616fd220d070bd36c38bd9d

            gerrit Gerrit Updater added a comment - "Chris Horn <chris.horn@hpe.com>" uploaded a new patch: https://review.whamcloud.com/45343 Subject: LU-15152 tests: auster reports wrong testsuite status Project: fs/lustre-release Branch: master Current Patch Set: 1 Commit: d8d28c2c21d6e79f1616fd220d070bd36c38bd9d

            People

              hornc Chris Horn
              hornc Chris Horn
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: