[Issue 150] Slaves with empty names destabilize Hudson operations

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[Issue 150] Slaves with empty names destabilize Hudson operations


------- Additional comments from [hidden email] Tue Nov 14 11:29:41 +0000 2006 -------
I tried with the latest stock version of Hudson 1.61, deployed on Tomcat, and
can see the same problems - adding slaves with empty fields leads to problems in
Hudson operations, like termination of executors, incorrect number of executors,
and inability of Hudson to execute builds until it's restarted.

If a slave with empty fields is configured to "utilize this slave as much as
possible" then all the started tasks will fail with the following weird exception:

Building remotely on
ERROR: Failed to mkdirs: http://HOSTNAME:9080/hudson/job/PROJECT/ws/
java.io.IOException: Failed to mkdirs:
        at hudson.FilePath.mkdirs(FilePath.java:69)
        at hudson.model.Project.checkout(Project.java:290)
        at hudson.model.Build$1.run(Build.java:307)
        at hudson.model.Run.run(Run.java:512)
        at hudson.model.Build.run(Build.java:289)
        at hudson.model.Executor.run(Executor.java:60)

If the slave with empty fields is configured with "leave this machine ..."
then all the executors are eventually reported DEAD in read, an no builds can be
done, and for some reason I see that most of my projects scheduled to run, even
though there were no changes in repositories, and after Hudson restart they are

I guess my point is that slaves with empty fields cause so many various problems
that they should be effectively disallowed or some defaults should be applied to
the empty fields, like, for example, "UNNAMED SLAVE #1", etc.

To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]