Hello, I'd expand that task in the middle and see if it was cancelled. It looks like a rescheduled job, because the agent went missing of the job took too much time. Hard to say just from the screenshot.
Cheers, Aravind On Wed, Mar 11, 2020 at 04:07:47 -0700, Yuri Lukyanov wrote: > I'm experiencing strange behavior with GoCD agents. > > My set up is the following: > GoCD version: 20.1.0 > Static agents as Docker images (based > on gocd/gocd-agent-ubuntu-16.04:v20.1.0). > All the docker containers are on the same machine (there are 4 of them). > All jobs have "Run one instance" on. > > I'm attaching a screenshot that I can not explain. > This is the log of a single run of a job in a pipeline. > > My understanding was that a job can be assigned to a single agent during > its execution. It can fail or succeed, but a single job is assigned to a > single agent at a time (for a single pipeline run). > And that the "Console" tab of the job shows the log messages of that run on > the agent. > > In the screenshot, there are log messages (in the same console) saying that > the same job started twice on different agents. > Could you explain how this can be possible at all? > > I thought I understand GoCD :) -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/20200311220938.puwvkzajhdgusljg%40arvindsv.com.
