Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] [Bug 551706] CDT's CI instance has stopped running jobs

Hello folks,

This recurring hang of our CI jobs happened again. We were due to release our M1 contribution for CDT9.10 / 2019-12 release tomorrow. At the moment due to this and tomorrow being Canadian Thanksgiving, I don't think we'll our contribution will be on time. Assuming no further delays I will aim to release M1 late Tuesday.


On Wed., Oct. 2, 2019, 10:00 Jonah Graham, <jonah@xxxxxxxxxxxxxxxx> wrote:
FYI - all builds on CDT's CI are hung at the moment. I hope they will be resolved soon, please follow bug below for more updates.

Thank you,
Jonah Graham
Kichwa Coders

---------- Forwarded message ---------
From: <bugzilla-daemon@xxxxxxxxxxx>
Date: Wed, 2 Oct 2019 at 09:59
Subject: [Bug 551706] CDT's CI instance has stopped running jobs
To: <jonah@xxxxxxxxxxxxxxxx>
Product/Component: Community / CI-Jenkins

            Bug ID: 551706
           Summary: CDT's CI instance has stopped running jobs
    Classification: Eclipse Foundation
           Product: Community
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: critical
          Priority: P3
         Component: CI-Jenkins
          Assignee: ci.admin-inbox@xxxxxxxxxxx
          Reporter: jonah@xxxxxxxxxxxxxxxx
                CC: webmaster@xxxxxxxxxxx
  Target Milestone: ---

CDT has stopped running builds. There are many build running waiting for
available executors, some for 3 days.

Some say: [1]
Still waiting to schedule task
‘cdt-agent-pod-v725h-58kxn’ is offline

Some say: [2]
Still waiting to schedule task
Waiting for next available executor

Are there hung machines? Alternatively has QNX's resource pack been removed
from CDT now the Doug is no longer project lead and that is preventing stuff
from running? If so, Kichwa Coders would like to assign its resource pack to
CDT please?


You are receiving this mail because:
You reported the bug.

Back to the top