Uploaded image for project: 'MariaDB Connector/C'
  1. MariaDB Connector/C
  2. CONC-759

Test unit.conc_async fails on signal 11 on arm64 (aarch64)

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      On arm64 the test fails on signal 11:

      unit.conc_async                          w4 [ fail ]
              Test ended at 2025-02-17 19:17:01
       
      CURRENT_TEST: unit.conc_async
      # ssl_port: 19030
      # socketname: /<<PKGBUILDDIR>>/builddir/mysql-test/var/tmp/4/mysqld.1.sock
      1..5
      # TLS server variables
      # --------------------
      # have_openssl: YES
      # have_ssl: YES
      # ssl_ca: /<<PKGBUILDDIR>>/mysql-test/std_data/cacert.pem
      # ssl_capath: 
      # ssl_cert: /<<PKGBUILDDIR>>/mysql-test/std_data/server-cert.pem
      # ssl_cipher: 
      # ssl_crl: 
      # ssl_crlpath: 
      # ssl_key: /<<PKGBUILDDIR>>/mysql-test/std_data/server-key.pem
      # version_ssl_library: OpenSSL 3.4.0 22 Oct 2024
      # Cipher in use: TLS_AES_256_GCM_SHA384
      # Peer certificate fingerprint: C138FD6B9BA9995AE1EF080034A60846FAA59705FD62EB91C7BAB673BFC6D5C20D6AD722998D8ADEC39C5EC65D96F663
      # Subject: /C=FI/ST=state or province within country, in other certificates in this file it is the same as L/L=location, usually an address but often ambiguously used/O=organization name, typically a company name/OU=organizational unit name, a division name within an organization/CN=localhost
      # --------------------
      # Testing against MySQL Server 11.4.5-MariaDB-1~bpo25.04.1~1739813055.603ca9b90ea+feature.
      # Host: Localhost via UNIX socket
      # Client library: 3.4.4
      ok 1 - test_async
      Bail out! Signal 11 thrown
       
      mysqltest failed with unexpected return code 255
      

      Full log at https://launchpadlibrarian.net/777266409/buildlog_ubuntu-plucky-arm64.mariadb_1%3A11.4.5-1~bpo25.04.1~1739813055.603ca9b90ea+feature.extend.mtr.to.big_BUILDING.txt.gz

      This was also reported by danblack as a comment in CONC-270.

      Attachments

        Issue Links

          Activity

            otto Otto Kekäläinen added a comment -

            Still visible in MariaDB 11.8.1:

            unit.conc_async                          w5 [ fail ]
                    Test ended at 2025-04-02 20:15:14
             
            CURRENT_TEST: unit.conc_async
            # ssl_port: 19090
            # socketname: /<<PKGBUILDDIR>>/builddir/mysql-test/var/tmp/5/mysqld.1.sock
            1..5
            # TLS server variables
            # --------------------
            # have_openssl: YES
            # have_ssl: YES
            # ssl_ca: /<<PKGBUILDDIR>>/mysql-test/std_data/cacert.pem
            # ssl_capath: 
            # ssl_cert: /<<PKGBUILDDIR>>/mysql-test/std_data/server-cert.pem
            # ssl_cipher: 
            # ssl_crl: 
            # ssl_crlpath: 
            # ssl_key: /<<PKGBUILDDIR>>/mysql-test/std_data/server-key.pem
            # version_ssl_library: OpenSSL 3.4.1 11 Feb 2025
            # Cipher in use: TLS_AES_256_GCM_SHA384
            # Peer certificate fingerprint: C138FD6B9BA9995AE1EF080034A60846FAA59705FD62EB91C7BAB673BFC6D5C20D6AD722998D8ADEC39C5EC65D96F663
            # Subject: /C=FI/ST=state or province within country, in other certificates in this file it is the same as L/L=location, usually an address but often ambiguously used/O=organization name, typically a company name/OU=organizational unit name, a division name within an organization/CN=localhost
            # --------------------
            # Testing against MySQL Server 11.8.1-MariaDB-2~bpo25.04.1~1743619672.b7bf6d3ee70+feature.
            # Host: Localhost via UNIX socket
            # Client library: 3.4.4
            ok 1 - test_async
            Bail out! Signal 11 thrown
             
             
            mysqltest failed with unexpected return code 255
            

            Full log: https://launchpadlibrarian.net/786050670/buildlog_ubuntu-plucky-arm64.mariadb_1%3A11.8.1-2~bpo25.04.1~1743619672.b7bf6d3ee70+feature.extend.mtr.to.big_BUILDING.txt.gz

            otto Otto Kekäläinen added a comment - Still visible in MariaDB 11.8.1: unit.conc_async w5 [ fail ] Test ended at 2025-04-02 20:15:14   CURRENT_TEST: unit.conc_async # ssl_port: 19090 # socketname: /<<PKGBUILDDIR>>/builddir/mysql-test/var/tmp/5/mysqld.1.sock 1..5 # TLS server variables # -------------------- # have_openssl: YES # have_ssl: YES # ssl_ca: /<<PKGBUILDDIR>>/mysql-test/std_data/cacert.pem # ssl_capath: # ssl_cert: /<<PKGBUILDDIR>>/mysql-test/std_data/server-cert.pem # ssl_cipher: # ssl_crl: # ssl_crlpath: # ssl_key: /<<PKGBUILDDIR>>/mysql-test/std_data/server-key.pem # version_ssl_library: OpenSSL 3.4.1 11 Feb 2025 # Cipher in use: TLS_AES_256_GCM_SHA384 # Peer certificate fingerprint: C138FD6B9BA9995AE1EF080034A60846FAA59705FD62EB91C7BAB673BFC6D5C20D6AD722998D8ADEC39C5EC65D96F663 # Subject: /C=FI/ST=state or province within country, in other certificates in this file it is the same as L/L=location, usually an address but often ambiguously used/O=organization name, typically a company name/OU=organizational unit name, a division name within an organization/CN=localhost # -------------------- # Testing against MySQL Server 11.8.1-MariaDB-2~bpo25.04.1~1743619672.b7bf6d3ee70+feature. # Host: Localhost via UNIX socket # Client library: 3.4.4 ok 1 - test_async Bail out! Signal 11 thrown     mysqltest failed with unexpected return code 255 Full log: https://launchpadlibrarian.net/786050670/buildlog_ubuntu-plucky-arm64.mariadb_1%3A11.8.1-2~bpo25.04.1~1743619672.b7bf6d3ee70+feature.extend.mtr.to.big_BUILDING.txt.gz

            People

              georg Georg Richter
              otto Otto Kekäläinen
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

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