Comment 1 for bug 1210205

This is caused by having two different job and build discovery paths that can overlap. The first path starts from the parent job and recursively scans for child jobs. Inside this, the code is scanning the builds and recursively scanning for child builds. When a child build is found that does not have a job, the job is created. The job based recursion will then attempt to create this job again. Both algorithms are needed as we can't assume that all jobs and builds have been deployed with the same children (these associations change over time).

The error messages are caused by the code using the exception path to handle this duplication.