From: Sean Christopherson <seanjc@google.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, KVM <kvm@vger.kernel.org>,
Cole Robinson <crobinso@redhat.com>
Subject: Re: The "memory" test is failing in the kvm-unit-tests CI
Date: Wed, 29 Mar 2023 12:11:38 -0700 [thread overview]
Message-ID: <ZCSNasVg+HBK0vI1@google.com> (raw)
In-Reply-To: <0dcae003-d784-d4e6-93a2-d8cc9a1e3bc1@redhat.com>
On Wed, Mar 29, 2023, Thomas Huth wrote:
>
> Hi,
>
> I noticed that in recent builds, the "memory" test started failing in the
> kvm-unit-test CI. After doing some experiments, I think it might rather be
> related to the environment than to a recent change in the k-u-t sources.
>
> It used to work fine with commit 2480430a here in January:
>
> https://gitlab.com/kvm-unit-tests/kvm-unit-tests/-/jobs/3613156199#L2873
>
> Now I've re-run the CI with the same commit 2480430a here and it is failing now:
>
> https://gitlab.com/thuth/kvm-unit-tests/-/jobs/4022074711#L2733
Can you provide the logs from the failing test, and/or the build artifacts? I
tried, and failed, to find them on Gitlab.
> Does anybody have an idea what could be causing this regression? The build
> in January used 7.0.0-12.fc37, the new build used 7.0.0-15.fc37, could that
> be related? Or maybe a different kernel version?
Nothing jumps to mind. Triaging this without at least the logs in going to be
painful.
next prev parent reply other threads:[~2023-03-29 19:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 9:50 The "memory" test is failing in the kvm-unit-tests CI Thomas Huth
2023-03-29 19:11 ` Sean Christopherson [this message]
2023-03-30 7:59 ` Thomas Huth
2023-03-30 19:37 ` Sean Christopherson
2023-04-03 8:23 ` Thomas Huth
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=ZCSNasVg+HBK0vI1@google.com \
--to=seanjc@google.com \
--cc=crobinso@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=thuth@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 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.