| << Back to previous view |
|
[QB-915] when appropriate node is not available, job runs on inappropriate node
|
|
| Status: | Closed |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 3.1.38 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Don Ross | Assigned To: | Robin Shen |
| Resolution: | Won't Fix | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Environment: | Centos5 server; Windows 2008 or Windows 2003 agents | ||
| Description |
|
I have a farm consisting of twelve agents; six Windows 2008 amd64, and six Windows 2003 x86.
These are further subdivided into agents running in two different Windows domains (englab.qa and englab.local). My node selection criteria is 'matching all specified criteria' - on Windows node - on any build agent - script evaluating to true: groovy: node.getAttribute("PROCESSOR_ARCHITECTURE").compareToIgnoreCase(vars.getValue("param_serverBitness")) == 0 - script evaluating to true: groovy: node.getAttribute("USERDNSDOMAIN").compareToIgnoreCase(vars.getValue("param_serverDomain")) == 0 The requestor is then able to specify values for param_serverBitness and param_serverDomain from drop-down lists. I also have a semaphore lock to prevent multiple jobs running on the same system at the same time: groovy: node.getResource("SingleThread", new java.util.concurrent.Semaphore(1)).acquire(); groovy: node.getResource("SingleThread").release(); I have found that, if I trigger four jobs all with the same values for param_serverBitness and param_serverDomain, the first three run on the nodes which satisfy those criteria. The fourth job runs on a randome node with the correct USERDNSDOMAIN, but the wrong PROCESSOR_ARCHITECTURE. |
| Comments |
| Comment by Don Ross [ 20/May/11 02:21 PM ] |
|
I tried with a much simpler rule, only one script query:
groovy: node.getAttribute("COMPUTERNAME").compareToIgnoreCase(vars.getValue("param_runHostName").tokenize('.')[0]) == 0 and it was not reproducible. So it may be because I have multiple criteria. |
| Comment by Robin Shen [ 21/May/11 12:43 AM ] |
| I tried the same, but can not reproduce. Can you please send backup of your database to [robin AT pmease DOT com] so that I can test here to see what happens? |
| Comment by Don Ross [ 26/May/11 11:06 PM ] |
|
I am sorry, I identified the problem. I had installed the 32-bit agent on my 64-bit system, so PROCESSOR_ARCHITECTURE was coming back wrong.
User error. |