qemu-devel
[Top][All Lists]
Advanced

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

Re: KVM call for 2016-06-16


From: Philippe Mathieu-Daudé
Subject: Re: KVM call for 2016-06-16
Date: Mon, 15 Jun 2020 11:45:17 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0

Hi Juan,

On 6/15/20 11:34 AM, Juan Quintela wrote:
> 
> Hi
> 
> Please, send any topic that you are interested in covering.
> There is already a topic from last call:

This topic was already discussed in the last call :)

> 
> Last minute suggestion after recent IRC chat with Alex Bennée and
> Thomas Huth:
> 
> "Move some of the build/CI infrastructure to GitLab."
> 
> Pro/Con?
> 
>  - GitLab does not offer s390x/ppc64el => keep Travis for these?
> 
> How to coordinate efforts?
> 
> What we want to improve? Priorities?
> 
> Who can do which task / is motivated.
> 
> What has bugged us recently:
> - Cross-build images (currently rebuilt all the time on Shippable)
> 
> Long term interests:
> 
> - Collect quality metrics
>   . build time
>   . test duration
>   . performances
>   . binary size
>   . runtime memory used
> 
> - Collect code coverage
> 
> Note, this is orthogonal to the "Gating CI" task Cleber is working on:
> https://www.mail-archive.com/qemu-devel@nongnu.org/msg688150.html
> 
> 
> 
> 
> At the end of Monday I will send an email with the agenda or the
> cancellation of the call, so hurry up.
> 
> After discussions on the QEMU Summit, we are going to have always open a
> KVM call where you can add topics.
> 
>  Call details:
> 
> By popular demand, a google calendar public entry with it
> 
>   
> https://www.google.com/calendar/embed?src=dG9iMXRqcXAzN3Y4ZXZwNzRoMHE4a3BqcXNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
> 
> (Let me know if you have any problems with the calendar entry.  I just
> gave up about getting right at the same time CEST, CET, EDT and DST).
> 
> If you need phone number details,  contact me privately
> 
> Thanks, Juan.
> 
> 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]