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

sanity test_411: fail to trigger a memory allocation error

Details

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

    Description

      This issue was created by maloo for Bob Glossman <bob.glossman@intel.com>

      This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/32b0aa4c-9502-11e7-ba84-5254006e85c2.

      The sub-test test_411 failed with the following error:

      fail to trigger a memory allocation error
      

      test_411 is very new. has been failing since 9/1
      some (all?) of the instances of FAIL have been seen on sles12sp2/sles12sp3

      more:
      https://testing.hpdd.intel.com/test_sets/8c6725ca-8f6c-11e7-b5c2-5254006e85c2
      https://testing.hpdd.intel.com/test_sets/0a6acf7c-8f8f-11e7-b67f-5254006e85c2

      Info required for matching: sanity 411

      Attachments

        Issue Links

          Activity

            [LU-9966] sanity test_411: fail to trigger a memory allocation error
            pjones Peter Jones added a comment -

            Landed for 2.12

            pjones Peter Jones added a comment - Landed for 2.12

            Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/32293/
            Subject: LU-9966 tests: sanity-411 check LBUG direct
            Project: fs/lustre-release
            Branch: master
            Current Patch Set:
            Commit: 18637db7ca6fa92ec6ea494a353a5ec46700a30e

            gerrit Gerrit Updater added a comment - Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/32293/ Subject: LU-9966 tests: sanity-411 check LBUG direct Project: fs/lustre-release Branch: master Current Patch Set: Commit: 18637db7ca6fa92ec6ea494a353a5ec46700a30e
            yujian Jian Yu added a comment - +1 on master branch: https://testing.whamcloud.com/test_sets/8e14dad8-c18f-11e8-a9d9-52540065bddc
            ys Yang Sheng added a comment -

            Yes, since the allocation is really depend on situation. So we should avoid to verify dd whether success or not. Anyway, I'll update the patch as this way.

            ys Yang Sheng added a comment - Yes, since the allocation is really depend on situation. So we should avoid to verify dd whether success or not. Anyway, I'll update the patch as this way.
            jhammond John Hammond added a comment -

            Logs show that some allocations are failing but dd is succeeding. Perhaps we should weaken the test to just check that we don't crash.

            jhammond John Hammond added a comment - Logs show that some allocations are failing but dd is succeeding. Perhaps we should weaken the test to just check that we don't crash.

            We see a different but related bug with Ubuntu18.

            simmonsja James A Simmons added a comment - We see a different but related bug with Ubuntu18.
            hornc Chris Horn added a comment - - edited

            Just a note: This issue is also seen with Lustre 2.11 on SLES15 RC4

            hornc Chris Horn added a comment - - edited Just a note: This issue is also seen with Lustre 2.11 on SLES15 RC4

            Yang Sheng (yang.sheng@intel.com) uploaded a new patch: https://review.whamcloud.com/32293
            Subject: LU-9966 tests: sanity-411 check LBUG direct
            Project: fs/lustre-release
            Branch: master
            Current Patch Set: 1
            Commit: eb5551388e81b16704c6655f6a2d0c469b9d5262

            gerrit Gerrit Updater added a comment - Yang Sheng (yang.sheng@intel.com) uploaded a new patch: https://review.whamcloud.com/32293 Subject: LU-9966 tests: sanity-411 check LBUG direct Project: fs/lustre-release Branch: master Current Patch Set: 1 Commit: eb5551388e81b16704c6655f6a2d0c469b9d5262

            > I think test_411 just intends to verify not hit on LBUG. So we can avoid to check dd whether success or not.
            > Does it necessary?

            YangSheng, yes we may do that, but we could also try to find a way to set the conditions that may cause dd to fail.

            bfaccini Bruno Faccini (Inactive) added a comment - > I think test_411 just intends to verify not hit on LBUG. So we can avoid to check dd whether success or not. > Does it necessary? YangSheng, yes we may do that, but we could also try to find a way to set the conditions that may cause dd to fail.
            bogl Bob Glossman (Inactive) added a comment - another on master: https://testing.hpdd.intel.com/test_sets/a0416dd0-2f8a-11e8-b6a0-52540065bddc

            People

              ys Yang Sheng
              maloo Maloo
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: