I think you are referring to so-called flyweight executor tasks. For
example, the parent task of a multi-configuration project. Because such
tasks typically don't require many system resources, they do not occupy
an executor. I have seen cases on our Jenkins installation where the
flyweight tas
The apparent interference might have been due to other things.
But does no one else have ghosts?
jb
On Thursday, January 26, 2017 at 3:27:12 PM UTC-5, John Bobinyec wrote:
>
>
> We have a pool of slaves. When a job is dispatched to one of them it is
> assigned to an executor on that machine.
We have a pool of slaves. When a job is dispatched to one of them it is
assigned to an executor on that machine. Oftentimes there is a very
similar job running on another machine but it's not assigned to an
executor. I call these ghosts. What do they do? How are they
dispatched? It seems