Message-Id: <1537559060.3146069.1516423416.0F09A000@webmail.messagingengine.com>
From: "Jean-Louis Fuchs" <ganwell@fangorn.ch>
To: alpine-devel@lists.alpinelinux.org
Cc: michael@wyraz.de
Precedence: list
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
Date: Fri, 21 Sep 2018 21:44:20 +0200
References: <c35bd4f4-5a3a-dc22-a808-4158925e6565@wyraz.de>
 <OF167A71D4.1C2F26FA-ON0025830D.0004ADBF-0025830D.0004F73B@notes.na.collabserv.com>
 <e8775f45-adff-2a6b-1a4d-ed7e5094ad56@wyraz.de>
 <63122645-4b33-c850-b30c-af77519f5f2d@jirutka.cz>
Subject: Re: [alpine-devel] Proposal: Multi-Arch matrix builds on travis-ci
In-Reply-To: <63122645-4b33-c850-b30c-af77519f5f2d@jirutka.cz>

Hi

On Wed, 19 Sep 2018, at 11:17, Jakub Jirutka wrote:

> I didn't use it in aports intentionally, because it's *very* slow. Many 
> aports would fail to build due to exceeding the time limit (50 minutes) 
> and it would significantly increase waiting time for all builds (due to 
> exhausted job queue).

There was or is bug in qemu-user-static, that made it terribly slow.  This version:

$> ./qemu-arm-static --version
qemu-arm version 2.9.1(qemu-2.9.1-2.fc26)

is definitely ok, I haven't tested any newer ones. In my opinion most builds should not fail due time limit on travis. BUT the tests sometimes do, after all its not the correct kernel. I am moving towards qemu-system using netboot for my development. netboot boots surprisingly consistent across architectures. You can append apkovl= to provision the VM.

Best,
   Jean-Louis


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---