Attachments (0)
Change History (9)
comment:1 by , 11 months ago
Component: | Core → Unit tests |
---|---|
Resolution: | → fixed |
Status: | new → closed |
comment:2 by , 11 months ago
Keywords: | jenkins added |
---|
comment:3 by , 11 months ago
Is it possible that there are too few free executors? I think the job is still waiting for a free one.
follow-up: 6 comment:4 by , 11 months ago
I didn't kill the rest of the queue. We have a single executor, so we go through the queue serially.
I could look into adding my home server as an executor, but I'd want to go through the current jobs to make certain they can be run on a separate machine.
comment:5 by , 11 months ago
We have a single executor, so we go through the queue serially.
OK, that explains it. I'll just wait ;)
comment:6 by , 11 months ago
Replying to taylor.smock:
I didn't kill the rest of the queue. We have a single executor, so we go through the queue serially.
I could look into adding my home server as an executor, but I'd want to go through the current jobs to make certain they can be run on a separate machine.
Not necessary. The server could also do more than one queue, but why? ;-)
follow-up: 8 comment:7 by , 11 months ago
I was just confused because Jenkins showed 4 different task which are "executed" but only one was really making progress.
comment:8 by , 11 months ago
Replying to GerdP:
I was just confused because Jenkins showed 4 different task which are "executed" but only one was really making progress.
I think being confused by Jenkins is totally normal. It's rather an exception if one understands what's going on. ;-)
comment:9 by , 11 months ago
IIRC, most of the jobs that were "executing" were parent jobs that were waiting on their children to execute. There was only one that was actually doing anything.
I killed the integration job that seemed to be stuck (~2 days).
For the record, it was stuck in
check-plugins
: