Re: [MirageOS-devel] [opam-devel] regular bulk builds: now with HTML output!

[Anil Madhavapeddy <anil@xxxxxxxxxx>]

On 8 Jan 2015, at 23:30, Jeremy Yallop <yallop@xxxxxxxxx> wrote:
> 
> On 8 January 2015 at 18:52, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote:
>> Greetings! I've been cleaning up the bulk build infrastructure for OPAM and 
>> will have a blog post about it in a few days, but in the meanwhile I thought 
>> you might like to see the output:
>> 
>> http://www.recoil.org/~avsm/opam-bulk/ (temporary URL)
> 
> Very nice indeed!  It's quite a leap in usability from the raw logs.
> 
> A few thoughts:
> 
> * displaying the "Sort by OS" / "Sort by Version" as tabs rather than
> columns if possible would avoid showing everything twice.

Absolutely.  Rather than continue to hack on this "rapidly put together"
HTML page, the next iteration will be based on the Zurb Foundation framework
and so use all the UI components from there (including tabs, pagination
and filtering by tags).  Volunteers for this are very welcome -- I can
document how the (rather simple) filesystem metadata works if anyone wants
to pull together a nicer frontend.

> 
> * occasionally there's a failure due to what look like infrastructure
> errors, e.g.
>      
> http://www.recoil.org/~avsm/opam-bulk/logs/local-ubuntu-14.04-ocaml-4.01.0/raw/blahcaml.html
>      
> http://www.recoil.org/~avsm/opam-bulk/logs/local-ubuntu-14.04-ocaml-4.01.0/raw/cmdliner.html
>  it'd be good to distinguish these from actual build failures if possible.

Getting Docker to work reliably has been challenging, even on a 
single host :-(  There doesn't seem to be a predictable error code from these
invocations, retrying is tricky.  I'm switching the scripts to BTRFS in case
that works out better.

> * it might be useful to display the revision (perhaps the repository
> commit id) somewhere --  perhaps in the URL, If there's a possibility
> of keeping multiple log sets around.

Yes agreed.  I'll put that into the next round of builds.  I also notice that
sometimes on Debian older revisions of packages are installed (and this happened
on the TLS stack a few times on is-mirage-broken as well).  Recording which
concrete versions got installed per OS would be a good step.

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel