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

unit.lf failed in buildbot

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.0(EOL), 10.1(EOL), 10.2(EOL)
    • N/A
    • Tests
    • None
    • kvm-fulltest --ps-protocol

    Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest/builds/8688/steps/test_3/logs/stdio

      unit.lf                                  w4 [ fail ]
      		 
              Test ended at 2017-05-08 08:42:15
      		 
       
      		 
      CURRENT_TEST: unit.lf
      		 
      # N CPUs: 4, atomic ops: gcc-atomics-smp
      		 
      1..7
      		 
      ok 1 - my_atomic_initialize() returned 0
      		 
      # Testing lf_pinbox (with my_thread_init) with 30 threads, 3000 iterations... 
      Bail out! Signal 11 thrown
      		 
      # 7 tests planned,  0 failed,  1 was last executed
      		 
       
      		 
       
      		 
      mysqltest failed with unexpected return code 255

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. MDEV-15670 unit.my_atomic failed in buildbot with Signal 11 thrown

          • Major - Major loss of function.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-14465 unit.lf failed in buildbot, sporadic

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-27088 Server crash on ARM (WMM architecture) due to missing barriers in lf-hash

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-28430 lf_alloc isn't safe on aarch64 (or ppc64le)

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

          Activity

            Ascending order - Click to sort in descending order
            elenst Elena Stepanova created issue -
            elenst Elena Stepanova made changes -
            Field Original Value New Value
            Fix Version/s 10.0 [ 16000 ]
            Affects Version/s 10.0 [ 16000 ]
            elenst Elena Stepanova made changes -
            elenst Elena Stepanova made changes -
            Affects Version/s 10.2 [ 14601 ]
            elenst Elena Stepanova made changes -
            Fix Version/s 10.2 [ 14601 ]
            svoj Sergey Vojtovich made changes -
            Assignee Sergey Vojtovich [ svoj ]
            svoj Sergey Vojtovich made changes -
            Status Open [ 1 ] Confirmed [ 10101 ]
            svoj Sergey Vojtovich made changes -
            Fix Version/s N/A [ 14700 ]
            Fix Version/s 10.2 [ 14601 ]
            Fix Version/s 10.0 [ 16000 ]
            Fix Version/s 10.1 [ 16100 ]
            Resolution Duplicate [ 3 ]
            Status Confirmed [ 10101 ] Closed [ 6 ]
            svoj Sergey Vojtovich made changes -
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 80932 ] MariaDB v4 [ 152215 ]
            monty Michael Widenius made changes -
            Assignee Sergey Vojtovich [ svoj ]
            Resolution Duplicate [ 3 ]
            Status Closed [ 6 ] Stalled [ 10000 ]
            danblack Daniel Black made changes -
            danblack Daniel Black made changes -
            danblack Daniel Black made changes -
            Resolution Fixed [ 1 ]
            Status Stalled [ 10000 ] Closed [ 6 ]

            People

              Unassigned Unassigned
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.