Details

    • Task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • N/A
    • N/A
    • Buildbot
    • None

    Description

      • Focus on the new buildbot (used in github branch protection checks)
      • [x] Find out which builds run which spider tests
      • Update buildbot to include spider tests in github mandatory checks when the spider code is touched

      Attachments

        Issue Links

          Activity

            ycp Yuchen Pei added a comment -

            vladbogo Thank you. I just re-ran the same builder
            amd64-ubuntu-2204-debug-ps on the commit I used above, but it still
            does not show the failure spider/bugfix.mdev_19866:

            I'm gonna try a brand new commit now, see if it makes any difference.

            ycp Yuchen Pei added a comment - vladbogo Thank you. I just re-ran the same builder amd64-ubuntu-2204-debug-ps on the commit I used above, but it still does not show the failure spider/bugfix.mdev_19866 : https://buildbot.mariadb.org/#/builders/534/builds/8216 https://buildbot.mariadb.org/#/grid?branch=bb-10.5-mdbf-535-test I'm gonna try a brand new commit now, see if it makes any difference.
            ycp Yuchen Pei added a comment - - edited

            Seems like the regexp fix works for most of the builders, but a few builders (e.g. amd64-centos-7) still do not show the new spider failure:

            https://buildbot.mariadb.org/#/grid?branch=bb-10.9-mdbf-535-test

            Do you know what could have caused this vladbogo?

            ycp Yuchen Pei added a comment - - edited Seems like the regexp fix works for most of the builders, but a few builders (e.g. amd64-centos-7) still do not show the new spider failure: https://buildbot.mariadb.org/#/grid?branch=bb-10.9-mdbf-535-test Do you know what could have caused this vladbogo ?
            vladbogo Vlad Bogolin added a comment -

            Hi. Buildbot uses a multi master setup where sub parts of the builders are managed by different master processes. The master process that handled amd64-centos-7 was not yet restarted with the new changes. That particular master handles all protected branches builders and there were running builds when I propagated the changes. Unfortunately buildbot requires a restart to propagate new changes which cancels all running builds. However, the changes will be propagated to all masters. Thanks for checking!

            vladbogo Vlad Bogolin added a comment - Hi. Buildbot uses a multi master setup where sub parts of the builders are managed by different master processes. The master process that handled amd64-centos-7 was not yet restarted with the new changes. That particular master handles all protected branches builders and there were running builds when I propagated the changes. Unfortunately buildbot requires a restart to propagate new changes which cancels all running builds. However, the changes will be propagated to all masters. Thanks for checking!
            ycp Yuchen Pei added a comment -

            vladbogo I see, thanks for explaining. Do you know when the change will be propagated to all masters?

            ycp Yuchen Pei added a comment - vladbogo I see, thanks for explaining. Do you know when the change will be propagated to all masters?
            ycp Yuchen Pei added a comment -

            vladbogo Yes I just checked amd64-centos-7 on a recent build and it did run the spider tests[1], thank you for fixing this.

            [1] https://buildbot.mariadb.org/#/builders/146/builds/25142

            ycp Yuchen Pei added a comment - vladbogo Yes I just checked amd64-centos-7 on a recent build and it did run the spider tests [1] , thank you for fixing this. [1] https://buildbot.mariadb.org/#/builders/146/builds/25142

            People

              vladbogo Vlad Bogolin
              ycp Yuchen Pei
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 0d
                  0d
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 0.95d
                  0.95d