[Buildbot-commits] [Buildbot] #2551: Triggered builds containing steps synchronized by a SlaveLock (counting or exclusive) are sometimes not run.

[Buildbot trac]

#2551: Triggered builds containing steps synchronized by a SlaveLock (counting or
exclusive) are sometimes not run.
---------------------+-------------------------
Reporter:  cmumford  |      Owner:
    Type:  defect    |     Status:  new
Priority:  major     |  Milestone:  undecided
 Version:  0.8.7p1   |   Keywords:  Triggerable
---------------------+-------------------------
 I have a test buildbot configuration with two builders (that build), one
 of which triggers six other test builds. There are only two test build
 slaves which use a SlaveLock to ensure that a slave only runs one test at
 a time. In this configuration if I make changes to the monitored Git
 repository, which in turn fires off four builds, there will often be
 several test slaves which are never run. There is no evidence in either
 the master or slave logs to indicate the cause (that I can see).

 Steps to reproduce:

 1. Expand the attached archive.
 2. $ cd bbtest/bbtest
 3. $ make # This starts both server and a few slaves.
 4. $ make bumpseveral; sleep 8; make bumpseveral
 5. Wait for builds/tests to finish (approx 1-2 minutes).
 6. $ tree /tmp/build_artifacts

 Each android build artifact should have six test results files as so:

 {{{
 /tmp/build_artifacts
 ├── build_0
 │   ├── android
 │   │   ├── test1
 │   │   ├── test1_results.txt
 │   │   ├── test2
 │   │   ├── test2_results.txt
 │   │   ├── test3
 │   │   ├── test3_results.txt
 │   │   ├── test4
 │   │   ├── test4_results.txt
 │   │   ├── test5
 │   │   ├── test5_results.txt
 │   │   ├── test6
 │   │   └── test6_results.txt
 │   └── gtk
 │       ├── test1
 │       ├── test2
 │       ├── test3
 │       ├── test4
 │       ├── test5
 │       └── test6
 }}}


 But sometimes you will see a build with one or more tests which are
 '''not''' run:

 {{{
 ├── build_2
 │   ├── android
 │   │   ├── test1
 │   │   ├── test2
 │   │   ├── test3
 │   │   ├── test4
 │   │   ├── test4_results.txt
 │   │   ├── test5
 │   │   ├── test5_results.txt
 │   │   ├── test6
 │   │   └── test6_results.txt
 │   └── gtk
 │       ├── test1
 │       ├── test2
 │       ├── test3
 │       ├── test4
 │       ├── test5
 │       └── test6
 }}}

 If you look in the waterfall or grid you will see that the test is not
 run.

 If I bump the maxCountForSlave's from 1 to 10 then I cannot reproduce the
 problem.

-- 
Ticket URL: <http://trac.buildbot.net/ticket/2551>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation