Investigate CQ volume drop at 12:18 PST |
||
Issue descriptionhttps://viceroy.corp.google.com/chrome_infra/Services/cq For page-level alerts, please post updates for this outage in the corresponding Outalator entry: https://o.corp.google.com/#Tickets:chrome-infra:::: Alert Details ------------------ Description: commit_queue/chromium is not running name: CriticalCQTaskDown current value: 0 threshold: Eq(0) for 10m alert fields: {service_name=commit_queue,job_name=chromium,proxy_zone=atl, } sent at: 2017-04-27 12:29:00 active since: 2017-04-27 12:27:35 (1 min 25 secs)
,
Apr 27 2017
No, its not. The cause was something else.
,
Apr 27 2017
[D2017-04-27T12:15:29.736453-07:00 24842 140278599853888 verification.tree_status:55] Issue 2846743002 is not blocked on tree status - the tree is open [D2017-04-27T12:15:29.737453-07:00 24842 140278599853888 async_push:315] Sending patch_ready_to_commit event to status app for issue 2846743002, patchset 1 [D2017-04-27T12:15:29.738613-07:00 24842 140278599853888 async_push:320] Sending patch_ready_to_commit event to event_mon for issue 2846743002, patchset 1 [D2017-04-27T12:15:29.741701-07:00 24842 140278599853888 infra_libs.event_mon.router:235] event_mon: POSTing events to https://play.googleapis.com/log [D2017-04-27T12:31:23.285341-07:00 4159 140322483750720 infra_libs.event_mon.config:145] event_mon: setting up monitoring.
,
Apr 27 2017
So, CQ python process crashed: [74381874.518542] python[24842]: segfault at 2736b59 ip 00007f9527a79ffe sp 00007fffd04cf838 error 4 in libc-2.19.so[7f95279e2000+1bb000] interestingly, a "nearby" processed died too [74381874.518557] python[24861]: segfault at 2736b59 ip 00007f9527a79ffe sp 00007f9521a3fb98 error 4 in libc-2.19.so[7f95279e2000+1bb000] So, i think the problem is super old host. TO be fixed by issue 573492 |
||
►
Sign in to add a comment |
||
Comment 1 by andyb...@chromium.org
, Apr 27 2017