From: Jon Turney <jon.turney@dronecode.org.uk>
To: Daisuke Fujimura <booleanlabel@gmail.com>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: scallywag error report
Date: Wed, 28 Jun 2023 13:55:43 +0100 [thread overview]
Message-ID: <1a364c43-1679-6739-ba79-d516d00a1205@dronecode.org.uk> (raw)
In-Reply-To: <CAA3frXQYE=Ysc4kKiq0UrnSK7=PApBx9YYtZ-b2HetUynrBG3A@mail.gmail.com>
On 28/06/2023 11:56, Daisuke Fujimura via Cygwin-apps wrote:
> I am reporting a scallywag error during git push.
>
> remote: scallywag: invoked on repository git/cygwin-packages/libhtp,
> by maintainer Daisuke Fujimura
> remote: scallywag: timeout waiting for GitHub to assign a wfr_id
> remote: scallywag: PLEASE REPORT THIS!
> remote: scallywag: build 6661 queued on github
> remote: scallywag: https://cygwin.com/cgi-bin2/jobs.cgi?id=6661
>
> The job is completed, but the status seems to remain pending.
Thanks for reporting this.
Yeah, this is an awkward part of the GitHub API we use here: all we get
back from the request to start the workflow is a "yes/no" response, so
we have to work out how to match the workflow id to our build number
ourselves.
I've repaired this job so it's reached it's final status.
I've temporarily increased the timeout here to two minutes (where we
wait for the just requested workflow to appear in the list of workflows
so we know it's id). I have an idea about a possibly better way to
implement this matching, but haven't yet got around to trying to
implement it yet...
prev parent reply other threads:[~2023-06-28 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 10:56 Daisuke Fujimura
2023-06-28 12:55 ` 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=1a364c43-1679-6739-ba79-d516d00a1205@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=booleanlabel@gmail.com \
--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).