From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>,
Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Subject: Re: CI Build Job Shows Pending but Github Actions Scallywag shows Success Completed
Date: Sat, 14 Aug 2021 12:32:04 +0100 [thread overview]
Message-ID: <829dfc1f-61af-d6bb-efeb-7979c0bf3891@dronecode.org.uk> (raw)
In-Reply-To: <c1fa2c77-1c4f-370e-4772-68116601b22a@SystematicSw.ab.ca>
On 13/08/2021 15:43, Brian Inglis wrote:
> CI build job 3160 gzip shown as still Pending
>
> https://cygwin.com/cgi-bin2/jobs.cgi?id=3160
>
> but Github Actions Scallywag #146 job status shows Success and each arch
> shows as Completed
>
> https://github.com/cygwin/scallywag/actions/runs/1125132438
Yeah, there's something not 100% reliable in the way this event is
processed (it seems like the metadata artifact url occasionally 404s if
we try to fetch it immediately after the job completes)
I've tried to add some resilience, but it seems it's still not there.
I caused this event to get reprocessed, so it's status should be up to
date now.
I'll continue working on it, but please let me know if this happens again.
prev parent reply other threads:[~2021-08-14 11:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 14:43 Brian Inglis
2021-08-14 11:32 ` Jon Turney [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=829dfc1f-61af-d6bb-efeb-7979c0bf3891@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=Brian.Inglis@SystematicSw.ab.ca \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).