public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: GitHub automation for Cygwin builds [Was: Updated: moreutils v0.65-1]
Date: Sun, 17 Jan 2021 06:15:38 +0100	[thread overview]
Message-ID: <240a782c-16b9-b829-df00-47e743ac3998@gmail.com> (raw)
In-Reply-To: <a7038ee6-0f58-2333-b51d-d5b829dde55f@cornell.edu>

On 16.01.2021 23:31, Ken Brown via Cygwin-apps wrote:
> On 1/16/2021 3:33 PM, Adam Dinwoodie wrote:
>> On Sat, 16 Jan 2021 at 20:22, Adam Dinwoodie wrote:
>>> Version 0.65-1 of moreutils has been uploaded and should be coming
>>> soon to a distribution server near you.

> 
> I assume you're quoting from https://cygwin.com/packaging/build.html.  
> Scallywag does have some limitations currently, but I think the 
> statement you quoted is obsolete.  I often have Scallywag deploy my 
> packages, as does Jon Turney.
> 
> The limitations I've bumped into are:
> 
> 1. Scallywag will time out after an hour on each arch

until now I was hit only during test. But I stil need to
deploy on our Git some of the heavy packages

> 
> 2. Several of my packages fail to build on x86 because of gcc crashes.

3. sometimes the failure is not in the build, but in missing or 
imperfect testing

> 
> I think these limitations are outweighed by the fact that a Scallywag 
> build is automatically triggered by a push to an official source repo 
> (https://cygwin.com/packaging/repos.html).  All maintainers can use this 
> without any special setup.

+1

> Ken

but of course Adam, more options are always better,

Thank for sharing
Marco

  reply	other threads:[~2021-01-17  5:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+kUOanKdcsMg1oHzTkBaaXxOF-qw+uoF7_w9CvTRgd_hRH-Gg@mail.gmail.com>
2021-01-16 20:33 ` Adam Dinwoodie
2021-01-16 22:31   ` Ken Brown
2021-01-17  5:15     ` Marco Atzeri [this message]
2021-01-17 15:33     ` Adam Dinwoodie
2021-05-09 14:40       ` Jon Turney
2021-06-06 17:19         ` Jon Turney
2021-06-06 17:37           ` ASSI
2021-06-06 18:32             ` Brian Inglis
2021-06-10 17:53               ` 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=240a782c-16b9-b829-df00-47e743ac3998@gmail.com \
    --to=marco.atzeri@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).