On 2019-01-22 14:42, Ed Maste wrote:
> On Tue, 22 Jan 2019 at 04:40, Thomas Huth wrote:
>>
>> Then I finally increased the CPUs back to 8 again, but stick with 8G of
>> RAM, and that indeed finished in time successfully:
>>
>> https://cirrus-ci.com/build/6218565876187136
>>
>> So yes, looks like
On Tue, 22 Jan 2019 at 04:40, Thomas Huth wrote:
>
> Then I finally increased the CPUs back to 8 again, but stick with 8G of
> RAM, and that indeed finished in time successfully:
>
> https://cirrus-ci.com/build/6218565876187136
>
> So yes, looks like 8 CPUs should work indeed, but I think you
On Tue, 22 Jan 2019 at 10:11, Thomas Huth wrote:
> PS: I also removed the V=1 in my tests since otherwise the log was way
> to verbose for my taste ... but that's likely really just a matter of taste.
I tend to run the 'make' step without V, and the 'make check' step
with V=1 -- the compile part
On 2019-01-21 17:30, Ed Maste wrote:
> On Mon, 21 Jan 2019 at 10:16, Ed Maste wrote:
>>
>> To confirm, I have another build running now with
>> echo "Running with hw.ncpu=$(sysctl -n hw.ncpu)"
>> added.
>
> Confirmed - https://cirrus-ci.com/build/5768962257190912:
> Running with hw.ncpu=8
>
>
On Mon, 21 Jan 2019 at 10:16, Ed Maste wrote:
>
> To confirm, I have another build running now with
> echo "Running with hw.ncpu=$(sysctl -n hw.ncpu)"
> added.
Confirmed - https://cirrus-ci.com/build/5768962257190912:
Running with hw.ncpu=8
If there is some sort of hanging test issue I could
Ed Maste writes:
> On Mon, 21 Jan 2019 at 06:03, Alex Bennée wrote:
>>
>> I should be able to add CirrusCI to the QEMU project github when we
>> merge. I see there is another revision coming in so I''ll wait for that
>> before I queue it up.
>
> Do you mean my eadd119 commit "cirrus: tail
On Mon, 21 Jan 2019 at 06:03, Alex Bennée wrote:
>
> I should be able to add CirrusCI to the QEMU project github when we
> merge. I see there is another revision coming in so I''ll wait for that
> before I queue it up.
Do you mean my eadd119 commit "cirrus: tail dmesg to see if this is
due to
On Mon, 21 Jan 2019 at 05:18, Thomas Huth wrote:
>
> Actually, scratch that Tested-by: My build timed out after 1 hour:
>
> https://cirrus-ci.com/task/5113243459649536
Interesting. My build reports successful completion after a bit under
1/2 hr: https://cirrus-ci.com/build/5717787416723456
I
ema...@freebsd.org writes:
> From: Ed Maste
>
> Signed-off-by: Ed Maste
> ---
> Changes since v2:
> * remove fontconfig and freetype2, noted by Thomas Huth
>
> After this patch is applied someone with appropriate permissions will
> need to add the Cirrus-CI application in GitHub.
I should
On 2019-01-21 10:13, Thomas Huth wrote:
> On 2019-01-18 15:47, ema...@freebsd.org wrote:
>> From: Ed Maste
>>
>> Signed-off-by: Ed Maste
>> ---
>> Changes since v2:
>> * remove fontconfig and freetype2, noted by Thomas Huth
>>
>> After this patch is applied someone with appropriate permissions
On 2019-01-18 15:47, ema...@freebsd.org wrote:
> From: Ed Maste
>
> Signed-off-by: Ed Maste
> ---
> Changes since v2:
> * remove fontconfig and freetype2, noted by Thomas Huth
>
> After this patch is applied someone with appropriate permissions will
> need to add the Cirrus-CI application in
From: Ed Maste
Signed-off-by: Ed Maste
---
Changes since v2:
* remove fontconfig and freetype2, noted by Thomas Huth
After this patch is applied someone with appropriate permissions will
need to add the Cirrus-CI application in GitHub.
.cirrus.yml | 16
MAINTAINERS | 8
12 matches
Mail list logo
