On Mon, 12 Nov 2018 at 22:32, Ryan Schmidt <ryandes...@macports.org> wrote:
> On Nov 12, 2018, at 15:25, db wrote:
> > On 11 Nov 2018, at 13:00, Ryan Schmidt wrote:
> >
> >> I'll probably need to write a script to pull all the failures out of the
> >> buildbot logs, since we don't have anything set up to do that yet. If
> >> there are ports you want to use, check whether any issues are filed
> >> against them in Trac before upgrading the OS.
> >
> > Whatever you write, could you add it to macports-contrib? I thought myself
> > to pull all failures to know beforehand if and what should/could be
> > upgraded from time to time, but it remains in my todo. It's a missing
> > feature of MacPorts, at least for those that build from source. Is this
> > information available throught the JSON API [1]?
> >
> > [1] https://build.macports.org/json/help
>
> What we really want is a web site where this information can more easily be
> seen. I'm not writing that web site now, but if I get around to the scripts
> and they give me the information we want, moving that into web space might be
> the next task on the list.
>
> This was a GSoC project that didn't get done.
>
> https://trac.macports.org/wiki/SummerOfCode#build-stats
Maybe better links with two documents:
https://github.com/macports/macports-webapp/tree/master/docs
> I don't really want the public making massive numbers of http requests to the
> buildmaster (which is what the script would do) because I fear it might be
> slow and clog up the bandwidth. I can run the scripts on the same network as
> the buildmaster and so not use up its bandwidth.
This is a no-go and it would takes forever anyway, even if there was
just a single person trying to do that (I know, I have a script :).
Mojca
