Travis CI timeouts for MacPorts builds

I fail to remember the last time one of my builds successfully passed Travis CI. All I see are timeouts [1]. Other peoples' jobs apparently make it through Travis OK, so I wander what I can do to increase my chances? [1] https://travis-ci.org/github/macports/macports-ports/jobs/724689780 -Ralph

"publishing" Tcl support functions used in Portfiles?

Hi, This may be considered a "not-done" but please bear with me and give me some pointers on how it might be done locally... Suppose you have developed a Tcl function in a Portfile (or a PortGroup) that performs a necessary job which you might sometimes want to be able to perform outside of a

Re: "publishing" Tcl support functions used in Portfiles?

On 2020-9-7 19:20 , René J.V. Bertin wrote: > Hi, > > This may be considered a "not-done" but please bear with me and give me some > pointers on how it might be done locally... > > Suppose you have developed a Tcl function in a Portfile (or a PortGroup) that > performs a necessary job which you

Re: Travis CI timeouts for MacPorts builds

On 2020-9-7 18:45 , Ralph Seichter wrote: > I fail to remember the last time one of my builds successfully passed > Travis CI. All I see are timeouts [1]. Other peoples' jobs apparently > make it through Travis OK, so I wander what I can do to increase my > chances? > > [1] https://travis-ci.org/g

Re: Travis CI timeouts for MacPorts builds

On Mon, 7 Sep 2020 at 10:46, Ralph Seichter wrote: > > I fail to remember the last time one of my builds successfully passed > Travis CI. All I see are timeouts [1]. Other peoples' jobs apparently > make it through Travis OK, so I wander what I can do to increase my > chances? By far the best thin

Re: Travis CI timeouts for MacPorts builds

> On Sep 7, 2020, at 08:50, Mojca Miklavec wrote: > > On Mon, 7 Sep 2020 at 10:46, Ralph Seichter wrote: >> >> I fail to remember the last time one of my builds successfully passed >> Travis CI. All I see are timeouts [1]. Other peoples' jobs apparently >> make it through Travis OK, so I wande

Re: Travis CI timeouts for MacPorts builds

I was wondering... Would à Linux machine with some virtualization method (libvirt?) be acceptable as CI runner? Any of you has experience in terms of performance? Also, Gitlab CI allows to attach personal runners to project very easily (just a package to install from the os package manager) . How

Re: Travis CI timeouts for MacPorts builds

* Joshua Root: >> [1] https://travis-ci.org/github/macports/macports-ports/jobs/724689780 > > It's just a matter of how long your port takes to build (including > installing all its dependencies). Notmuch, which is what was built in the job [1], is small and builds in less than a minute on my Mac

Re: Travis CI timeouts for MacPorts builds

* Mojca Miklavec: > If you volunteer to do some research / work in this area ... that > would likely be the most significant step in "increasing your chances" I actually have some experience in this field. I use GitLab (Omnibus edition), Docker, and GitLab Runners inside Docker for CI/CD. That's

Re: Travis CI timeouts for MacPorts builds

* Ryan Schmidt: > I feel that the Azure Pipelines are already giving us good results on > current systems, and we could probably turn off the Travis builds for > the systems that Azure also covers. That seems like a reasonable approach to me. -Ralph

Re: "publishing" Tcl support functions used in Portfiles?

On Monday September 07 2020 22:39:50 Joshua Root wrote: Thanks, will have a look. >You do it like this: > > >In that proc, $mport is an identifier that was returned from mportopen, >and the code being

Re: Travis CI timeouts for MacPorts builds

On 2020-9-8 02:44 , Ralph Seichter wrote: > * Joshua Root: > >>> [1] https://travis-ci.org/github/macports/macports-ports/jobs/724689780 >> >> It's just a matter of how long your port takes to build (including >> installing all its dependencies). > > Notmuch, which is what was built in the job [1

Re: Travis CI timeouts for MacPorts builds

On Mon, 7 Sep 2020 at 18:44, Ralph Seichter wrote: > * Joshua Root: > > >> [1] https://travis-ci.org/github/macports/macports-ports/jobs/724689780 > > > > It's just a matter of how long your port takes to build (including > > installing all its dependencies). > > Notmuch, which is what was built in

Re: Travis CI timeouts for MacPorts builds

On Mon, 7 Sep 2020 at 18:25, Ruben Di Battista wrote: > > I was wondering... Would à Linux machine with some virtualization method > (libvirt?) be acceptable as CI runner? This is something we've been looking at, among others. Now, a Linux machine with libvirt is probably not entirely legal, but

Re: Travis CI timeouts for MacPorts builds

* Mojca Miklavec: > It tries to install dependencies as binaries, provided the binaries > are available. Tries being the operative word here. ;-) > We should figure out: > - which dependencies time out > - why they are not installed from (the private) binary package repository I'm guessing that

Re: Travis CI timeouts for MacPorts builds

* Mojca Miklavec: > What we need is: > - a list of recipes to set up images for a bunch of different macOS > versions (as far back into history as possible) > - a recipe for how to fire up a VM, do something basic (port install > foo) and trash the result Looking at the Travis CI config and the r

Re: Factors determining binary archivability

Good point. It had slipped my mind to take a look at the buildbot waterfall view... thanks for the reminder. -- Jason Liu On Mon, Sep 7, 2020 at 2:55 AM Ryan Schmidt wrote: > > > On Sep 7, 2020, at 01:09, Jason Liu wrote: > > > It's a relief to see that the 10.15 and 10.12 builds completed >