You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nuttx.apache.org by "Matias N." <ma...@imap.cc> on 2021/05/18 17:13:44 UTC

CI stuck?

I noticed CI wasn't running jobs and found several runs from 8 hrs ago which were stuck with "internal error" reports. I canceled those (event though there weren't actually running) to see if the queued ones were picked up (which doesn't seem to be the case). Anyone knows what could be happening?

Best,
Matias

Re: CI stuck?

Posted by Brennan Ashton <ba...@brennanashton.com>.
Yeah I had tried to communicate that information here as well, this is why
I had suggested the cancellation jobs in the first place, when you enabled
(thank you!).  The graph is by workflow not job so it makes our usage look
a lot worse but yeah I agree we need to do what we can to improve our
resource usage not just for ourselves and I really appreciate the work you
have been putting into this!

--Brennan

On Tue, May 18, 2021, 11:14 AM Matias N. <ma...@imap.cc> wrote:

> Thanks Brennan. So we will have to wait it out it seems.
> In the meantime I looked around in the Apache builds list and found a
> thread from April
> related to issues with GA. This thread included an analysis of which were
> the worst offenders
> in CI time and we sadly came out on top. You can see a graph here as well:
> https://cwiki.apache.org/confluence/display/BUILDS/GitHub+Actions+status
>
> I'm hoping that with CMake we can really improve our build time (that is
> the impression
> I get locally as well).
>
> Best,
> Matias
>
> On Tue, May 18, 2021, at 15:10, Brennan Ashton wrote:
> > I saw this a few days ago when GitHub was having some issues and it looks
> > like they have an active outage now as well that is recovering so I would
> > suspect that.
> >
> > https://www.githubstatus.com/
> >
> > --Brennan
> >
> > On Tue, May 18, 2021, 10:17 AM Matias N. <matias@imap.cc <mailto:
> matias%40imap.cc>> wrote:
> >
> > > I noticed CI wasn't running jobs and found several runs from 8 hrs ago
> > > which were stuck with "internal error" reports. I canceled those (event
> > > though there weren't actually running) to see if the queued ones were
> > > picked up (which doesn't seem to be the case). Anyone knows what could
> be
> > > happening?
> > >
> > > Best,
> > > Matias
> >
>

Re: CI stuck?

Posted by "Matias N." <ma...@imap.cc>.
Thanks Brennan. So we will have to wait it out it seems.
In the meantime I looked around in the Apache builds list and found a thread from April
related to issues with GA. This thread included an analysis of which were the worst offenders
in CI time and we sadly came out on top. You can see a graph here as well:
https://cwiki.apache.org/confluence/display/BUILDS/GitHub+Actions+status

I'm hoping that with CMake we can really improve our build time (that is the impression
I get locally as well).

Best,
Matias

On Tue, May 18, 2021, at 15:10, Brennan Ashton wrote:
> I saw this a few days ago when GitHub was having some issues and it looks
> like they have an active outage now as well that is recovering so I would
> suspect that.
> 
> https://www.githubstatus.com/
> 
> --Brennan
> 
> On Tue, May 18, 2021, 10:17 AM Matias N. <matias@imap.cc <mailto:matias%40imap.cc>> wrote:
> 
> > I noticed CI wasn't running jobs and found several runs from 8 hrs ago
> > which were stuck with "internal error" reports. I canceled those (event
> > though there weren't actually running) to see if the queued ones were
> > picked up (which doesn't seem to be the case). Anyone knows what could be
> > happening?
> >
> > Best,
> > Matias
> 

Re: CI stuck?

Posted by Brennan Ashton <ba...@brennanashton.com>.
I saw this a few days ago when GitHub was having some issues and it looks
like they have an active outage now as well that is recovering so I would
suspect that.

https://www.githubstatus.com/

--Brennan

On Tue, May 18, 2021, 10:17 AM Matias N. <ma...@imap.cc> wrote:

> I noticed CI wasn't running jobs and found several runs from 8 hrs ago
> which were stuck with "internal error" reports. I canceled those (event
> though there weren't actually running) to see if the queued ones were
> picked up (which doesn't seem to be the case). Anyone knows what could be
> happening?
>
> Best,
> Matias