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

main.status failed in buildbot

Details

    Description

      http://buildbot.askmonty.org/buildbot/builders/p8-rhel6-bintar-debug/builds/995/steps/test/logs/stdio

      main.status                              w3 [ fail ]
      		 
              Test ended at 2017-06-28 12:40:00
      		 
       
      		 
      CURRENT_TEST: main.status
      		 
      --- /home/buildbot/maria-slave/p8-rhel6-bintar-debug/build/mysql-test/r/status.result	2017-06-28 01:12:20.050010021 -0400
      		 
      +++ /home/buildbot/maria-slave/p8-rhel6-bintar-debug/build/mysql-test/r/status.reject	2017-06-28 12:39:59.950010019 -0400
      		 
      @@ -278,9 +278,9 @@
      		 
       CALL p1();
      		 
       1
      		 
       1
      		 
      -SELECT 9;
      		 
      -9
      		 
      -9
      		 
      +SELECT 10;
      		 
      +10
      		 
      +10
      		 
       disconnect con1;
      		 
       connection default;
      		 
       DROP PROCEDURE p1;
      		 
       
      		 
      mysqltest: Result length mismatch

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-8510 main.status test fails sporadically in buildbot

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            alice Alice Sherepa added a comment -

            also on 10.3 http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos73-amd64/builds/2967/steps/mtr-tcmllc/logs/stdio

            alice Alice Sherepa added a comment - also on 10.3 http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos73-amd64/builds/2967/steps/mtr-tcmllc/logs/stdio
            tturenko Timofey Turenko added a comment - - edited

            10.3 ES, sles15:

            main.status w3 [ fail ]
            Test ended at 2020-02-19 05:17:05

            CURRENT_TEST: main.status
            — /home/timofey_turenko_mariadb_com/mtr-big-test/MariaDBEnterprise/mysql-test/main/status.result 2020-02-19 04:01:56.000000000 +0100
            +++ /home/timofey_turenko_mariadb_com/mtr-big-test/MariaDBEnterprise/mysql-test/main/status.reject 2020-02-19 05:17:05.044114001 +0100
            @@ -280,9 +280,9 @@
            CALL p1();
            1
            1
            -SELECT 9;
            -9
            -9
            +SELECT 10;
            +10
            +10
            disconnect con1;
            connection default;
            DROP PROCEDURE p1;

            mysqltest: Result length mismatch

            • skipping '/var/tmp/mtr/3/log/main.status/'
            tturenko Timofey Turenko added a comment - - edited 10.3 ES, sles15: main.status w3 [ fail ] Test ended at 2020-02-19 05:17:05 CURRENT_TEST: main.status — /home/timofey_turenko_mariadb_com/mtr-big-test/MariaDBEnterprise/mysql-test/main/status.result 2020-02-19 04:01:56.000000000 +0100 +++ /home/timofey_turenko_mariadb_com/mtr-big-test/MariaDBEnterprise/mysql-test/main/status.reject 2020-02-19 05:17:05.044114001 +0100 @@ -280,9 +280,9 @@ CALL p1(); 1 1 -SELECT 9; -9 -9 +SELECT 10; +10 +10 disconnect con1; connection default; DROP PROCEDURE p1; mysqltest: Result length mismatch skipping '/var/tmp/mtr/3/log/main.status/'
            sanja Oleksandr Byelkin added a comment -

            it is failed sporadically but really very rare... OK, I will try to repeat or understand...

            sanja Oleksandr Byelkin added a comment - it is failed sporadically but really very rare... OK, I will try to repeat or understand...
            sanja Oleksandr Byelkin added a comment -

            The test coult global execution by query_id, probably with some condition SP/PS can be reprepare and rerun, which makes the test fail by counting one more query (or something can be done in parallel thread).

            The test fails once per month on buildbot and non of 10000 run on my computer.

            I think continue with the finding cause is just a wasting time.

            sanja Oleksandr Byelkin added a comment - The test coult global execution by query_id, probably with some condition SP/PS can be reprepare and rerun, which makes the test fail by counting one more query (or something can be done in parallel thread). The test fails once per month on buildbot and non of 10000 run on my computer. I think continue with the finding cause is just a wasting time.
            marko Marko Mäkelä added a comment -

            Recent occurrence on 10.8:

            main.status                              w12 [ fail ]
            		 
                    Test ended at 2022-11-10 07:58:53
            		 
            CURRENT_TEST: main.status
            		 
            --- /home/buildbot/amd64-debian-10/build/mysql-test/main/status.result	2022-11-10 07:53:17.000000000 +0000
            		 
            +++ /home/buildbot/amd64-debian-10/build/mysql-test/main/status.reject	2022-11-10 07:58:53.234855338 +0000
            		 
            @@ -280,9 +280,9 @@
            		 
             CALL p1();
            		 
             1
            		 
             1
            		 
            -SELECT 9;
            		 
            -9
            		 
            -9
            		 
            +SELECT 10;
            		 
            +10
            		 
            +10
            		 
             disconnect con1;
            		 
             connection default;
            		 
             DROP PROCEDURE p1;
            		 
            mysqltest: Result length mismatch

            According to the cross-reference, this test fails in this way at least weekly in some branch, sometimes several times per day. These failures can occur also on the mandatory "branch protection" builders, as was the case above.

            marko Marko Mäkelä added a comment - Recent occurrence on 10.8 : main.status w12 [ fail ] Test ended at 2022-11-10 07:58:53 CURRENT_TEST: main.status --- /home/buildbot/amd64-debian-10/build/mysql-test/main/status.result 2022-11-10 07:53:17.000000000 +0000 +++ /home/buildbot/amd64-debian-10/build/mysql-test/main/status.reject 2022-11-10 07:58:53.234855338 +0000 @@ -280,9 +280,9 @@ CALL p1(); 1 1 -SELECT 9; -9 -9 +SELECT 10; +10 +10 disconnect con1; connection default; DROP PROCEDURE p1; mysqltest: Result length mismatch According to the cross-reference, this test fails in this way at least weekly in some branch, sometimes several times per day. These failures can occur also on the mandatory "branch protection" builders, as was the case above.
            marko Marko Mäkelä added a comment -

            This failure variant is also mentioned in a comment of MDEV-8510, including some root cause analysis by kastauyra and a link to a possible fix:

            I have changed the testcase to use wait_until_count_sessions.inc (Threads_connected decrement happens very late in the disconnect): https://github.com/percona/percona-server/pull/1679. The diff contains semi-related changes of reverting that previously added dump

            marko Marko Mäkelä added a comment - This failure variant is also mentioned in a comment of MDEV-8510 , including some root cause analysis by kastauyra and a link to a possible fix: I have changed the testcase to use wait_until_count_sessions.inc (Threads_connected decrement happens very late in the disconnect): https://github.com/percona/percona-server/pull/1679 . The diff contains semi-related changes of reverting that previously added dump

            People

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