[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MirageOS-devel] mirageos 3 beta: let's do it!


  • To: Mindy Preston <mindy@xxxxxxxxxxxxxxxxxxx>
  • From: Anil Madhavapeddy <anil@xxxxxxxxxx>
  • Date: Tue, 17 Jan 2017 11:42:30 +0000
  • Cc: "mirageos-devel@xxxxxxxxxxxxxxxxxxxx" <mirageos-devel@xxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 17 Jan 2017 11:42:47 +0000
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=recoil.org; h=content-type :mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=Vg2kqL18DXTmZYv0qkRydFPMrfvzCVSqWL2V9RtRz9XV14ouI0j oJQXMm2igTUlTpWujpab18AVlie4mcouEp49g9INz8EG+/c5Ofo+kFr7P2cVUSEw vmPl+IYfJXAfSDrSPYUvcqUrSVo3I726w9XMpP9MHwn2p62w3iLmyf+4=
  • List-id: Developer list for MirageOS <mirageos-devel.lists.xenproject.org>

On 16 Jan 2017, at 11:46, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote:
> 
> On 13 Jan 2017, at 19:37, Mindy <mindy@xxxxxxxxxxxxxxxxxxx> wrote:
>> 
>> Hi folks,
>> 
>> I've just created a new repository 
>> (https://github.com/mirage/mirageos-3-beta) where the MirageOS 3 beta will 
>> be staged.
>> 
>> As discussed in our IRC meeting on 16 November 2016, this will be a 
>> repository with versioned package definitions and archive references for 
>> those packages included in MirageOS 3.  For many more details, see the 
>> inaugural issue at https://github.com/mirage/mirageos-3-beta/issues/1 .  If 
>> you maintain a Mirage package, I would especially appreciate your attention 
>> there.
>> 
>> I hope we'll have the full set of packages there early next week. :)
> 
> Epic! In preparation for this, I've added in support to the DataKit CI for 
> bulk builds. It can do builds with and without an extra remote (mirage-dev), 
> so we should be able to differentially spot errors.
> 
> https://ci.ocaml.io/mirage/opam-repository/ref/heads/bulk
> 
> It still needs a CLI tool to parse the build results, which I'm going to work 
> on this week, and then I will mail the list with how to use it.  If anyone 
> wants from the community wants to help out with triaging failures, it would 
> be a very handy thing to have assistance while we are busy breaking the 
> universe with the staging trees :-)

I've now added bulk builds for opam-repository with and without mirage-dev, and 
run a bulk build.  The prototype CLI tool is still being cleaned up, but I do 
have the initial results of the differential run (which is all we care about 
right now :-)

The (x -> y) represents the versions installed before and after the mirage-dev 
remote was added:

datakit (0.8.0 -> dev~mirage) fails now
datakit-client (0.8.0 -> 0.8.0) fails now
datakit-github (0.8.1 -> 0.8.1) fails now
datakit-server (0.8.0 -> 0.8.0) fails now
dns (0.18.1 -> dev~mirage) fails now
dog (0.2.1 -> 0.2.1) fails now
ezirmin (0.1.0 -> 0.1.0) fails now
hvsock (0.11.1 -> dev~mirage) fails now
jitsu (0.3.0 -> 0.3.0) fails now
jitsu-xapi (0.0.1 -> 0.0.1) fails now
mirage-block-xen (1.4.0 -> dev~mirage) still broken
mirage-entropy-xen (0.3.0 -> 0.3.0) fails now
mirage-git (1.6.0 -> 1.6.0) fails now
mirage-irmin (0.9.8 -> 0.9.8) fails now
mirage-net-xen (1.6.1 -> dev~mirage) still broken
mirage-qubes (0.3 -> dev~mirage) fails now
mirage-xen (2.6.0 -> dev~mirage) broken before and now builds
mirage-xen-minios (0.8.0 -> 0.8.0) fails now
nbd (2.1.1 -> dev~mirage) fails now
protocol-9p (0.8.0 -> dev~mirage) fails now
qcow (0.7.0 -> 0.7.0) fails now
qcow-format (0.5.0 -> dev~mirage) fails now
vhd-format (0.8.0 -> dev~mirage) fails now
vpnkit (0.0.0 -> 0.0.0) fails now
xenctrl (0.9.30 -> dev~mirage) broken before and now builds

cheers,
Anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.