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

main.ssl_7937 failed with timeout in buildbot on Windows

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.2
    • 10.2.11
    • Tests
    • None

    Description

      http://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/1864/steps/test/logs/stdio

      main.ssl_7937 'ssl'                      w1 [ fail ]  timeout after 2700 seconds
              Test ended at 2016-12-10 23:36:59
       
      Test case timeout after 2700 seconds
       
      == D:/win32-debug/build/mysql-test/var/1/log/ssl_7937.log == 
      create procedure have_ssl()
      select if(variable_value > '','yes','no') as 'have_ssl'
        from information_schema.session_status
      where variable_name='ssl_cipher';
      mysql --ssl-ca=cacert.pem -e "call test.have_ssl()"
       
       == D:/win32-debug/build/mysql-test/var/1/tmp/analyze-timeout-mysqld.1.err ==
      SHOW PROCESSLIST;
      Id	User	Host	db	Command	Time	State	Info	Progress
      5	root	localhost:52654	NULL	Query	0	init	SHOW PROCESSLIST	0.000
       
      mysqltest failed but provided no output
      The result from queries just before the failure was:
      < snip >
      create procedure have_ssl()
      select if(variable_value > '','yes','no') as 'have_ssl'
        from information_schema.session_status
      where variable_name='ssl_cipher';
      mysql --ssl-ca=cacert.pem -e "call test.have_ssl()"
      

      Attachments

        Issue Links

          Activity

            People

              wlad Vladislav Vaintroub
              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.