From: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
To: "Thomas Huth" <thuth@redhat.com>,
"Daniel P. Berrangé " <berrange@redhat.com>,
qemu-devel@nongnu.org
Cc: "Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>,
"Alex Benn é e" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daud é " <philmd@linaro.org>
Subject: Re: [PATCH 0/2] gitlab: expose installed package info in build logs
Date: Thu, 25 Jul 2024 13:20:51 +0300 [thread overview]
Message-ID: <h6czh.1irp2u56t07@linaro.org> (raw)
In-Reply-To: <e60c7b68-a3b2-4144-aebd-1110f40192e2@redhat.com>
On Thu, 25 Jul 2024 12:56, Thomas Huth <thuth@redhat.com> wrote:
>On 25/07/2024 11.42, Manos Pitsidianakis wrote:
>> Hello Daniel,
>>
>> On Wed, 24 Jul 2024 12:55, "Daniel P. Berrangé" <berrange@redhat.com> wrote:
>>> Many times we see a build job start failing, we wonder if the installed
>>> packages have changed since the last passing build. We can rarely
>>> diagnose this, however, since we only have the new container image, not
>>> the old one.
>>>
>>
>> APT allows you to specify to pin package versions when installing; wouldn't
>> that help ensure our tests are deterministic?
>
>Even if tests would be more deterministic that way, I also don't think
>that's what we want: We would test with backlevel packages that users are
>not using (since they'll normally use the latest version of a package from a
>certain version of a distro). So in our CI, we would not be able to
>reproduce the issues that the users are seeing on their systems.
>
Definitely, but the current testing makes it harder to discern the lines
between QEMU regression and QEMU not working with latest updates. If we
had e.g. a pinned job and a "latest" job disagreeing we'd know the
cause. Of course that means extra CI minutes, maintainer upkeep etc etc,
I know, but this was my reasoning, I don't dismiss testing for what
users experience. :)
Manos
next prev parent reply other threads:[~2024-07-25 10:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 9:55 [PATCH 0/2] gitlab: expose installed package info in build logs Daniel P. Berrangé
2024-07-24 9:55 ` [PATCH 1/2] gitlab: record installed packages in /packages.txt in containers Daniel P. Berrangé
2024-07-24 9:55 ` [PATCH 2/2] gitlab: display /packages.txt in build jobs Daniel P. Berrangé
2024-07-24 11:14 ` [PATCH 0/2] gitlab: expose installed package info in build logs Alex Bennée
2024-07-25 7:06 ` Philippe Mathieu-Daudé
2024-07-25 9:42 ` Manos Pitsidianakis
2024-07-25 9:56 ` Thomas Huth
2024-07-25 10:20 ` Manos Pitsidianakis [this message]
2024-07-25 10:00 ` Daniel P. Berrangé
2024-07-25 10:14 ` Alex Bennée
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=h6czh.1irp2u56t07@linaro.org \
--to=manos.pitsidianakis@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@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).