qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cleber Rosa <crosa@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Willian Rampazzo <wrampazz@redhat.com>,
	Wainer Moschetta <wainersm@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: QEMU CI failed due to canceled download
Date: Thu, 25 Feb 2021 14:24:02 -0500	[thread overview]
Message-ID: <20210225192402.GD1074102@amachine.somewhere> (raw)
In-Reply-To: <e8880ea6-7bc0-df19-4355-2c0b59c3d087@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]

On Thu, Feb 25, 2021 at 05:51:08AM +0100, Thomas Huth wrote:
> 
>  Hi,
> 
> I just faced this failure in the CI:
> 
>  https://gitlab.com/thuth/qemu/-/jobs/1053467007#L73
> 
> I thought we'd handle CANCEL as "skipped"? Why did this
> cause the CI to fail?
>

Hi Thomas,

Like Wainer pointed out, your expectations are correct.  CANCEL behaves
like a skip, but because the test was underway, rather than never
tried, Avocado calls it that way.

So, in this particular case, the test was actually interrupted, and it
was interrupted while downloading the Fedora 31 image, which it
*shouldn't* be doing during the test.  The "get-vm-images" target
defined in tests/Makefile.include is a prerequisite for
"check-acceptance", so that those files get downloaded before the
Avocado job even starts.

It looks like that on c401c058a1c a TARGETS variable was introduced
with a different format than it was coming from the main Makefile.
And, IIUC, that made the "get-vm-images" succeed because there was
no matching architecture to download.

I've reproduced the issue on my system, and I'm sending a patch with
a proposed fix.

Thanks,
- Cleber.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2021-02-25 19:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25  4:51 QEMU CI failed due to canceled download Thomas Huth
2021-02-25 13:37 ` Wainer dos Santos Moschetta
2021-02-25 19:24 ` Cleber Rosa [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210225192402.GD1074102@amachine.somewhere \
    --to=crosa@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=wainersm@redhat.com \
    --cc=wrampazz@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).