New issue
Advanced search Search tips

Issue 923571 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jan 18
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 0
Type: Bug



Sign in to add a comment

CQ run is not ending even though all paladins have ended

Project Member Reported by semenzato@chromium.org, Jan 18 (4 days ago)

Issue description

http://cros-goldeneye/chromeos/healthmonitoring/buildDetails?buildbucketId=8923974631222945120

It shows as "running" but all paladins are either green or red and have ended hours ago.

 

Comment 1 by vapier@chromium.org, Jan 18 (4 days ago)

if you look at the summary and the master logs, you can see that the master hasn't received any results from betty-arcnext-paladin.  so you should see where that communication broke down.

Comment 2 by semenzato@chromium.org, Jan 18 (4 days ago)

Cc: jclinton@chromium.org
Owner: athilenius@chromium.org
I will try to narrow down the cause, but I still won't know how to fix it.

Comment 3 by jclinton@chromium.org, Jan 18 (4 days ago)

Labels: OS-Chrome
Owner: jclinton@chromium.org
Status: Started (was: Untriaged)
It's the CIDB hang from issue 890053. I will use gdb to send a socket close event to the hung process. That will rescue the build.

Comment 4 by jclinton@chromium.org, Jan 18 (4 days ago)

Owner: athilenius@chromium.org
Status: Fixed (was: Started)
Alec killed the master paladin. The run results were lost but the immediate issue was fixed. The next run should be fine; this happens every few months. We should be completely off of CIDB in two quarters.

Sign in to add a comment