qemu-devel
[Top][All Lists]
Advanced

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

Re: [PULL 00/21] machine + QOM queue, 2020-10-05


From: Thomas Huth
Subject: Re: [PULL 00/21] machine + QOM queue, 2020-10-05
Date: Tue, 6 Oct 2020 20:43:44 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0

On 06/10/2020 18.14, Igor Mammedov wrote:
On Tue, 6 Oct 2020 17:42:28 +0200
Paolo Bonzini <pbonzini@redhat.com> wrote:

On 06/10/20 17:23, Igor Mammedov wrote:
Looks like travis-ci lost previous authorizations to my github repo,
but giving a new one didn't help.

Something wrong with current QEMU master, travis-ci doesn't recognize QEMU repo 
a valid anymore.

Interesting, I use Travis->Gitlab integration and even though builds are
still triggered, they don't appear in the Gitlab CI page.  So the
configuration is okay, but something seems to be wrong on the Travis side.

If one enables access to all repositories on account, then even if travis-ci
doesn't show QEMU repo as accessible one, it seems that there is a new build in
'received' state, maybe it will start building eventually.

It works for me (via my github account):

 https://travis-ci.com/github/huth/qemu/builds/188441775

... maybe it was just a temporary hickup?

Anyway, we do not test macOS on Travis anymore (see commit 22a231950c50d3), so this is likely not helpful for Eduardo's original problem... Cirrus-CI is the way to go if you need macOS test coverage.

 Thomas




reply via email to

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