All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marc-André Lureau" <mlureau@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Michael Roth" <mdroth@linux.vnet.ibm.com>,
	"John Snow" <jsnow@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] test-qga failures on Fedora 24
Date: Thu, 8 Dec 2016 02:47:16 -0500 (EST)	[thread overview]
Message-ID: <414279889.3011871.1481183236280.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAFEAcA8y2q1HDg0fL0kPLyySfNmPUpR2jCk1rzMhm1kcbzcBhQ@mail.gmail.com>

Hi

----- Original Message -----
> On 7 July 2016 at 00:02, Michael Roth <mdroth@linux.vnet.ibm.com> wrote:
> > Quoting John Snow (2016-07-06 17:41:32)
> >>
> >>
> >> On 07/06/2016 06:20 PM, Michael Roth wrote:
> >> > Quoting Marc-André Lureau (2016-07-06 16:40:52)
> >> >>> Here's the meat of it:
> >> >>>
> >> >>>   LINK  tests/test-qga
> >> >>> GTESTER tests/test-qga
> >> >>> **
> >> >>> ERROR:/home/bos/jhuston/src/qemu/tests/test-qga.c:266:test_qga_get_fsinfo:
> >> >>> assertion failed ret: GenericError realpath("/sys/dev/block/8:17"): No
> >> >>> such file or directory
> >> >>> GTester: last random seed: R02S9d55aa8939b9bd797279bd3f69d33466
> >> >>> **
> >> >>> ERROR:/home/bos/jhuston/src/qemu/tests/test-qga.c:685:test_qga_blacklist:
> >> >>> assertion failed ret: GenericError realpath("/sys/dev/block/8:17"): No
> >> >>> such file or directory
> >> >>> GTester: last random seed: R02Sb9bc461c2129c284f83033dca27827c6
> >> >>> /home/bos/jhuston/src/qemu/tests/Makefile.include:684: recipe for
> >> >>> target
> >> >>> 'check-tests/test-qga' failed
> >> >>> make: *** [check-tests/test-qga] Error 1
> >> >>>
> >> >>>
> >> >>> Any clues as to what's gone awry?
> 
> >> Good news: The problem went away.
> >>
> >> It was likely due to an external XFS drive I have that perhaps didn't
> >> properly register as ejected. I unmounted it and re-mounted it and now
> >> everything's fine.
> >>
> >> I'm not sure where it got 8:17, though. I guess mtab was stale?
> >
> > Yah, that would explain it. The values are pulled from mtab via
> > getmntent()
> 
> I just ran into this today too (in my case due to an external
> USB mass storage device that was powered-down without being
> unmounted). It's kind of annoying that the test fails: why should
> it care at all about what block devices you happen to have
> on your system, whether they're mounted or busted or otherwise ?
> 

Since guest-get-fsinfo isn't always succeeding, I propose to either handle errors gracefully and/or to move it with other tests under QGA_TEST_SIDE_EFFECTING.

QGA_TEST_SIDE_EFFECTING is supposed to succeed under a test VM/container, it's probably best to just move the test there.

      reply	other threads:[~2016-12-08  7:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-06 21:08 [Qemu-devel] test-qga failures on Fedora 24 John Snow
2016-07-06 21:40 ` Marc-André Lureau
2016-07-06 22:20   ` Michael Roth
2016-07-06 22:41     ` John Snow
2016-07-06 23:02       ` Michael Roth
2016-12-07 11:48         ` Peter Maydell
2016-12-08  7:47           ` Marc-André Lureau [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=414279889.3011871.1481183236280.JavaMail.zimbra@redhat.com \
    --to=mlureau@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.