Wainer dos Santos Moschetta writes:
> Hi all,
>> Conclusion
>> ==
>>
>> I think generally the state of QEMU's CI has improved over the last few
>> years but we still have a number of challenges caused by its distributed
>> nature and test stability. We are still re-active to failures
Cleber Rosa writes:
> On Thu, Mar 14, 2019 at 03:57:06PM +, Alex Bennée wrote:
>>
>> Hi,
>>
>> As we approach stabilisation for 4.0 I thought it would be worth doing a
>> review of the current state of CI and stimulate some discussion of where
>> it is working for us and what could be
On Thu, Mar 14, 2019 at 03:57:06PM +, Alex Bennée wrote:
>
> Hi,
>
> As we approach stabilisation for 4.0 I thought it would be worth doing a
> review of the current state of CI and stimulate some discussion of where
> it is working for us and what could be improved.
>
> Testing in Build
Hi all,
On 03/14/2019 12:57 PM, Alex Bennée wrote:
Hi,
As we approach stabilisation for 4.0 I thought it would be worth doing a
review of the current state of CI and stimulate some discussion of where
it is working for us and what could be improved.
Testing in Build System
> On Mar 15, 2019, at 23:12, Stefan Hajnoczi wrote:
>
> On Thu, Mar 14, 2019 at 03:57:06PM +, Alex Bennée wrote:
>> As we approach stabilisation for 4.0 I thought it would be worth doing a
>> review of the current state of CI and stimulate some discussion of where
>> it is working for us
Ed Vielmetti writes:
> There are a couple of options hosted at Packet - Shippable, Codefresh, and
> Drone. I perhaps know more about Drone than the others. Each of them have a
> supported/sponsored version which can be used to produce arm64 binaries
> natively.
>
> I'll admit to dropping into
There are a couple of options hosted at Packet - Shippable, Codefresh, and
Drone. I perhaps know more about Drone than the others. Each of them have a
supported/sponsored version which can be used to produce arm64 binaries
natively.
I'll admit to dropping into this conversation in mid-stream
Ed Vielmetti writes:
> We have been trying to merge the Gitlab runner patches for arm64
> for over a year now; see
>
> https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/725
Yes I found that one. I'm trying to work out exactly how there build
system works. It seems to build all
On 15/03/19 17:28, Peter Maydell wrote:
> On Fri, 15 Mar 2019 at 15:12, Stefan Hajnoczi wrote:
>> How should all sub-maintainers be checking their pull requests?
>>
>> We should have information and a strict policy on minimum testing of
>> pull requests. Right now I imagine it varies a lot
On Fri, 15 Mar 2019 at 15:12, Stefan Hajnoczi wrote:
> How should all sub-maintainers be checking their pull requests?
>
> We should have information and a strict policy on minimum testing of
> pull requests. Right now I imagine it varies a lot between
> sub-maintainers.
>
> For my block pull
Stefan Hajnoczi writes:
> On Thu, Mar 14, 2019 at 03:57:06PM +, Alex Bennée wrote:
>> As we approach stabilisation for 4.0 I thought it would be worth doing a
>> review of the current state of CI and stimulate some discussion of where
>> it is working for us and what could be improved.
>
>
We have been trying to merge the Gitlab runner patches for arm64
for over a year now; see
https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/725
I have not yet sorted out who at Gitlab has the ability to get
this change implemented - their management structure is
not something that I
On Thu, Mar 14, 2019 at 03:57:06PM +, Alex Bennée wrote:
> As we approach stabilisation for 4.0 I thought it would be worth doing a
> review of the current state of CI and stimulate some discussion of where
> it is working for us and what could be improved.
Thanks for this summary and for all
On 15/03/19 03:53, Fam Zheng wrote:
>> [+] I currently test:
>> - windows crossbuilds
>> - S390, AArch32, AArch64, PPC64 Linux
>> (SPARC currently disabled because of the migration-test flakiness)
>> - OSX
>> - FreeBSD, OpenBSD, NetBSD via the tests/vm setup
>> - various x86-64 configs:
> On Mar 15, 2019, at 17:58, Alex Bennée wrote:
>
>
> Fam Zheng writes:
>
>>> On Mar 15, 2019, at 16:57, Alex Bennée wrote:
>>>
>>> I had installed the gitlab-runner from the Debian repo but it was out
>>> of date and didn't seem to work correctly.
>>
>> If there can be a sidecar x86
Peter Maydell writes:
> On Fri, 15 Mar 2019 at 09:05, Alex Bennée wrote:
>>
>>
>> Peter Maydell writes:
>> > [+] I currently test:
>> > - windows crossbuilds
>>
>> We did have this with shippable but had to disable it when the upstream
>> repo went down. We could re-enable if we can rebuild
On Fri, 15 Mar 2019 at 09:05, Alex Bennée wrote:
>
>
> Peter Maydell writes:
> > [+] I currently test:
> > - windows crossbuilds
>
> We did have this with shippable but had to disable it when the upstream
> repo went down. We could re-enable if we can rebuild it and cache our
> docker images
Daniel P. Berrangé writes:
> On Fri, Mar 15, 2019 at 09:34:27AM +, Alex Bennée wrote:
>>
>> Daniel P. Berrangé writes:
>>
>> > On Thu, Mar 14, 2019 at 03:57:06PM +, Alex Bennée wrote:
>> >> Docker Images
>> >> =
>> >>
>> >> The addition of docker has unlocked the ability
On Fri, Mar 15, 2019 at 09:34:27AM +, Alex Bennée wrote:
>
> Daniel P. Berrangé writes:
>
> > On Thu, Mar 14, 2019 at 03:57:06PM +, Alex Bennée wrote:
> >> Docker Images
> >> =
> >>
> >> The addition of docker has unlocked the ability to build a lot more
> >> tests as well
Fam Zheng writes:
>> On Mar 15, 2019, at 16:57, Alex Bennée wrote:
>>
>> I had installed the gitlab-runner from the Debian repo but it was out
>> of date and didn't seem to work correctly.
>
> If there can be a sidecar x86 box next to the test bot, it can be the
> controller node which runs
On Thu, Mar 14, 2019 at 06:22:44PM +, Peter Maydell wrote:
> On Thu, 14 Mar 2019 at 15:57, Alex Bennée wrote:
> > Testing in the Cloud
> >
> >
> > After BuildBot went out-of-service we have been relying heavily on Travis
> > as our primary CI platform. This has been
> On Mar 15, 2019, at 16:57, Alex Bennée wrote:
>
> I had installed the gitlab-runner from the Debian repo but it was out
> of date and didn't seem to work correctly.
If there can be a sidecar x86 box next to the test bot, it can be the
controller node which runs gitlab-runner, the test
Daniel P. Berrangé writes:
> On Thu, Mar 14, 2019 at 03:57:06PM +, Alex Bennée wrote:
>> Docker Images
>> =
>>
>> The addition of docker has unlocked the ability to build a lot more
>> tests as well as compile testing on a much wider range of distros. I
>> think there are two
Peter Maydell writes:
> On Thu, 14 Mar 2019 at 15:57, Alex Bennée wrote:
>> Testing in the Cloud
>>
>>
>> After BuildBot went out-of-service we have been relying heavily on Travis
>> as our primary CI platform. This has been creaking somewhat under the
>> strain and while
Fam Zheng writes:
>> On Mar 15, 2019, at 02:22, Peter Maydell wrote:
>>
>> On Thu, 14 Mar 2019 at 15:57, Alex Bennée wrote:
>>> Testing in the Cloud
>>>
>>>
>>> After BuildBot went out-of-service we have been relying heavily on Travis
>>> as our primary CI platform. This
> On Mar 15, 2019, at 02:22, Peter Maydell wrote:
>
> On Thu, 14 Mar 2019 at 15:57, Alex Bennée wrote:
>> Testing in the Cloud
>>
>>
>> After BuildBot went out-of-service we have been relying heavily on Travis
>> as our primary CI platform. This has been creaking
On Thu, 14 Mar 2019 at 15:57, Alex Bennée wrote:
> Testing in the Cloud
>
>
> After BuildBot went out-of-service we have been relying heavily on Travis
> as our primary CI platform. This has been creaking somewhat under the
> strain and while we have a large test matrix its
On Thu, Mar 14, 2019 at 03:57:06PM +, Alex Bennée wrote:
> Docker Images
> =
>
> The addition of docker has unlocked the ability to build a lot more
> tests as well as compile testing on a much wider range of distros. I
> think there are two outstanding areas that need improvement
Hi,
As we approach stabilisation for 4.0 I thought it would be worth doing a
review of the current state of CI and stimulate some discussion of where
it is working for us and what could be improved.
Testing in Build System
===
Things seem to be progressing well in this
29 matches
Mail list logo
