public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Cc: Brian.Inglis@SystematicSw.ab.ca
Subject: Re: Scallywag Download log archive not working
Date: Sun, 30 Oct 2022 08:27:45 -0600	[thread overview]
Message-ID: <d76f07bd-e891-2210-536d-a804cd0d71b8@SystematicSw.ab.ca> (raw)

On 2022-10-30 07:15, Jon Turney wrote:
> On 24/10/2022 22:10, Brian Inglis wrote:
>> When I run a Github Actions Scallywag job and it completes, and I look at the 
>> job logs, I can no longer download the log archive, although I can still view 
>> each raw log.

> Are you saying the 'gear' icon is absent, doesn't have a "download log archive" 
> entry, or has the entry but it doesn't work?

Icon and entry present, but didn't work: after some delay, blue (progress) line 
crawled across tab, but download did not start, and log did not appear in 
download status bar.
Works okay now: may have been JavaScript server load if nothing changed?

> (Note that it's GitHub's annoying policy that you must be signed in to github to 
> view the logs)

Auto-logged in (Remember me) to allow interaction

-- 
Take care. Thanks, Brian Inglis			Calgary, Alberta, Canada

La perfection est atteinte			Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter	not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer	but when there is no more to cut
			-- Antoine de Saint-Exupéry

             reply	other threads:[~2022-10-30 14:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-30 14:27 Brian Inglis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-24 21:10 Brian Inglis
2022-10-30 13:15 ` Jon Turney

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=d76f07bd-e891-2210-536d-a804cd0d71b8@SystematicSw.ab.ca \
    --to=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).