On Mon, 8 Jan 2024, Alex Williamson wrote:
On Mon, 8 Jan 2024 23:32:04 +0530 (IST)
Vivek Kashyap wrote:
On Mon, 8 Jan 2024, Alex Williamson wrote:
On Mon, 8 Jan 2024 18:42:19 +0530 (IST)
Vivek Kashyap wrote:
...
As I've stated above, for libvirt we should consider only passing it via
Hi Samuel,
On 8/1/24 18:15, Samuel Tardieu wrote:
The shix machine has been designed and used at Télécom Paris from 2003
to 2010. It had been added to QEMU in 2005 and has not been maintained
since. Since nobody is using the physical board anymore nor interested
in maintaining the QEMU port, it
On Mon, Jan 08, 2024 at 17:59:06 +0100, Andrea Bolognani wrote:
> Notable changes compared to 7.0.0, the most recent version that
> we had capabilities for until now:
>
> * SPICE support is no longer compiled in;
>
> * uses of -no-acpi are replaced with -M virt,acpi=off;
>
> * -netdev uses
On Mon, Jan 08, 2024 at 17:59:05 +0100, Andrea Bolognani wrote:
> The vexpress machine has never supported ACPI. This fact has
> been silently ignored by QEMU so far, but recent versions have
> started reporting attempts to use the combination as an error.
>
> The other features (APIC, PAE) are al
On Mon, Jan 08, 2024 at 11:43:23 +0100, Andrea Bolognani wrote:
> Signed-off-by: Andrea Bolognani
> ---
> ci/integration.yml | 42 +-
> 1 file changed, 21 insertions(+), 21 deletions(-)
Reordering the entries made this very unpleasant to review.
Reviewed
On Mon, Jan 08, 2024 at 11:43:22 +0100, Andrea Bolognani wrote:
> These are jobs are supposed to be running tests using a QEMU
> binary built from the latest upstream sources, but right now
> they're just doing the same thing as the other jobs for the
> target. Use the correct job templates.
>
> S
On Mon, Jan 08, 2024 at 18:06:42 +0100, Jiri Denemark wrote:
> Signed-off-by: Jiri Denemark
> ---
> NEWS.rst | 8
> 1 file changed, 8 insertions(+)
>
> diff --git a/NEWS.rst b/NEWS.rst
> index dc40602c72..9675f12cb4 100644
> --- a/NEWS.rst
> +++ b/NEWS.rst
> @@ -17,6 +17,14 @@ v10.0.0 (
On Mon, Jan 08, 2024 at 18:06:41 +0100, Jiri Denemark wrote:
> During post-copy migration (once it actually switches to post-copy mode)
> dirty memory pages are continued to be migrated iteratively, while the
> destination can explicitly request a specific page to be migrated before
> the iterative
On Mon, Jan 08, 2024 at 18:06:40 +0100, Jiri Denemark wrote:
> We enable various migration capabilities according to the flags passed
> to a migration API. Missing support for such capabilities results in an
> error because they are required by the corresponding flag. This patch
> adds support for
On Mon, Jan 08, 2024 at 18:06:39 +0100, Jiri Denemark wrote:
> The migration cookie contains two bitmaps of migration capabilities:
> supported and automatic. qemuMigrationParamsCheck expects the letter so
> lets make it more obvious by renaming the parameter as remoteAuto.
>
> Signed-off-by: Jiri
On Mon, Jan 08, 2024 at 18:06:38 +0100, Jiri Denemark wrote:
> Signed-off-by: Jiri Denemark
> ---
> src/qemu/qemu_migration_params.c | 50
> 1 file changed, 25 insertions(+), 25 deletions(-)
Reviewed-by: Peter Krempa
_
On Mon, Jan 08, 2024 at 18:06:37 +0100, Jiri Denemark wrote:
> Signed-off-by: Jiri Denemark
> ---
> src/qemu/qemu_migration_params.c | 12 +++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
Reviewed-by: Peter Krempa
___
Devel mailing list
Signed-off-by: Andrea Bolognani
---
NEWS.rst | 6 ++
1 file changed, 6 insertions(+)
diff --git a/NEWS.rst b/NEWS.rst
index dc40602c72..b9e8f11aed 100644
--- a/NEWS.rst
+++ b/NEWS.rst
@@ -17,6 +17,12 @@ v10.0.0 (unreleased)
* **New features**
+ * qemu: Support clusters in CPU topology
Signed-off-by: Andrea Bolognani
---
docs/formatcaps.rst | 2 +-
docs/formatdomain.rst | 18 ++
2 files changed, 11 insertions(+), 9 deletions(-)
diff --git a/docs/formatcaps.rst b/docs/formatcaps.rst
index 3cccf70882..5c678f0787 100644
--- a/docs/formatcaps.rst
+++ b/docs/form
Since aarch64 doesn't support CPU hotplug at the moment, we have
to get a bit creative.
While the 'query-cpus-fast' output is taken directly from a VM
configured as
16
the 'query-hotpluggable-cpus' output is constructed by hand
starting from the former and using the 'x86-dies' test
The default number of CPU clusters is 1, and values other than
that one are currently rejected by all hypervisor drivers.
Signed-off-by: Andrea Bolognani
---
src/bhyve/bhyve_command.c| 5 +
src/conf/cpu_conf.c | 16 +++-
src/c
For machines that don't expose useful information through sysfs,
the dummy ID 0 is used.
https://issues.redhat.com/browse/RHEL-7043
Signed-off-by: Andrea Bolognani
---
src/conf/capabilities.c | 5 +-
src/conf/capabilities.h | 1 +
src/conf/schemas
https://issues.redhat.com/browse/RHEL-7043
Signed-off-by: Andrea Bolognani
---
src/qemu/qemu_command.c | 4 +++-
tests/qemuxml2argvdata/cpu-hotplug-startup.x86_64-latest.args | 2 +-
tests/qemuxml2argvdata/cpu-numa-disjoint.x86_64-latest.args | 2 +-
tests
Mention that support for the "dies" attribute was introduced in
libvirt 6.1.0 and clarify that the ability to use non-default
values is subject to architecuture and machine limitations.
Signed-off-by: Andrea Bolognani
---
docs/formatdomain.rst | 16 ++--
1 file changed, 10 insertions
This makes it so libvirt can obtain accurate information about
guest CPUs from QEMU, and should make it possible to correctly
perform operations such as CPU hotplug.
Of course this is mostly moot at the moment: only aarch64 can use
CPU clusters, and CPU hotplug is not yet implemented on that
archi
Signed-off-by: Andrea Bolognani
---
.../cpu-topology5.aarch64-latest.args | 31 +++
tests/qemuxml2argvdata/cpu-topology5.xml | 17 ++
tests/qemuxml2argvtest.c | 1 +
3 files changed, 49 insertions(+)
create mode 100644 tests/qemuxml2argv
The data is taken from an HPE Apollo 70 machine, which uses
aarch64 CPUs. It is interesting for us because non-dummy
information about CPU clusters is exposed through sysfs.
Signed-off-by: Andrea Bolognani
---
.../linux-basic-clusters/system/cpu |1 +
.../linux-basic-clusters/syste
Signed-off-by: Andrea Bolognani
---
src/qemu/qemu_capabilities.c | 2 ++
src/qemu/qemu_capabilities.h | 1 +
tests/qemucapabilitiesdata/caps_7.1.0_ppc64.xml | 1 +
tests/qemucapabilitiesdata/caps_7.1.0_x86_64.xml | 1 +
tests/qemucapabiliti
Edited for brevity. Full version:
$ git fetch https://gitlab.com/abologna/libvirt.git cpu-clusters
Depends on:
https://lists.libvirt.org/archives/list/devel@lists.libvirt.org/thread/IDFVKTZ6SKD6X6NI4DHM6JMXMQEVNVDL/
Andrea Bolognani (11):
tests: Add hostcpudata for machine with CPU clust
On Mon, 8 Jan 2024 23:32:04 +0530 (IST)
Vivek Kashyap wrote:
> On Mon, 8 Jan 2024, Alex Williamson wrote:
>
> > On Mon, 8 Jan 2024 18:42:19 +0530 (IST)
> > Vivek Kashyap wrote:
> >
> >> ...
> As I've stated above, for libvirt we should consider only passing it via
> the 'secret' o
On Mon, Jan 08, 2024 at 05:29:41PM +, Daniel P. Berrangé wrote:
> On Mon, Jan 08, 2024 at 05:59:06PM +0100, Andrea Bolognani wrote:
> > Notable changes compared to 7.0.0, the most recent version that
> > we had capabilities for until now:
> >
> > * SPICE support is no longer compiled in;
>
>
On Mon, 8 Jan 2024, Alex Williamson wrote:
On Mon, 8 Jan 2024 18:42:19 +0530 (IST)
Vivek Kashyap wrote:
...
As I've stated above, for libvirt we should consider only passing it via
the 'secret' object.
Sounds good. Will follow this up.
Alex - will you be working on the qemu update?
I
On Mon, Jan 08, 2024 at 05:59:06PM +0100, Andrea Bolognani wrote:
> Notable changes compared to 7.0.0, the most recent version that
> we had capabilities for until now:
>
> * SPICE support is no longer compiled in;
Presumably that's just your dev machine lacking spice-server-devel,
since upstre
On 1/8/24 18:15, Samuel Tardieu wrote:
The 16MiB flash device is only used by the deprecated shix machine.
Its code it old and unmaintained, and has never been adapted to the
QOM architecture. It still contains debug statements and uses global
variables. It is time to deprecate it.
Signed-off-by
On 1/8/24 18:15, Samuel Tardieu wrote:
The shix machine has been designed and used at Télécom Paris from 2003
to 2010. It had been added to QEMU in 2005 and has not been maintained
since. Since nobody is using the physical board anymore nor interested
in maintaining the QEMU port, it is time to d
Signed-off-by: Jiri Denemark
---
NEWS.rst | 8
1 file changed, 8 insertions(+)
diff --git a/NEWS.rst b/NEWS.rst
index dc40602c72..9675f12cb4 100644
--- a/NEWS.rst
+++ b/NEWS.rst
@@ -17,6 +17,14 @@ v10.0.0 (unreleased)
* **New features**
+ * qemu: Enable postcopy-preempt migration
During post-copy migration (once it actually switches to post-copy mode)
dirty memory pages are continued to be migrated iteratively, while the
destination can explicitly request a specific page to be migrated before
the iterative process gets to it (which happens when a guest wants to
read a page
We enable various migration capabilities according to the flags passed
to a migration API. Missing support for such capabilities results in an
error because they are required by the corresponding flag. This patch
adds support for additional optional capability we may want to enable
for a given API
The migration cookie contains two bitmaps of migration capabilities:
supported and automatic. qemuMigrationParamsCheck expects the letter so
lets make it more obvious by renaming the parameter as remoteAuto.
Signed-off-by: Jiri Denemark
---
src/qemu/qemu_migration_params.c | 6 +++---
src/qemu/q
Signed-off-by: Jiri Denemark
---
src/qemu/qemu_migration_params.c | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/src/qemu/qemu_migration_params.c b/src/qemu/qemu_migration_params.c
index 79fe6e97c8..9de6c08021 100644
--- a/src/qemu/qemu_migration_params.c
+++ b/s
Signed-off-by: Jiri Denemark
---
src/qemu/qemu_migration_params.c | 50
1 file changed, 25 insertions(+), 25 deletions(-)
diff --git a/src/qemu/qemu_migration_params.c b/src/qemu/qemu_migration_params.c
index 9de6c08021..b02a8af8d5 100644
--- a/src/qemu/qemu_migr
This is technically a v2 of my recent "Introduce
VIR_MIGRATE_POSTCOPY_PREEMPT flag", but the two series share exactly two
lines of code (those defining a new QEMU_MIGRATION_CAP_POSTCOPY_PREEMPT
enum item) so I'm just sending it as a separate series.
More details about this feature can be found in
On Fri, Jan 05, 2024 at 17:31:50 +0100, Jiri Denemark wrote:
> On Fri, Jan 05, 2024 at 17:11:57 +0100, Peter Krempa wrote:
> > On Fri, Jan 5, 2024 at 4:55 PM Jiri Denemark wrote:
> >
> > > During post-copy migration (once it actually switches to post-copy mode)
> > > dirty memory pages are contin
Notable changes compared to 7.0.0, the most recent version that
we had capabilities for until now:
* SPICE support is no longer compiled in;
* uses of -no-acpi are replaced with -M virt,acpi=off;
* -netdev uses JSON.
Signed-off-by: Andrea Bolognani
---
.../qemu_8.2.0-virt.aarch64.xml
The vexpress machine has never supported ACPI. This fact has
been silently ignored by QEMU so far, but recent versions have
started reporting attempts to use the combination as an error.
The other features (APIC, PAE) are also not relevant to the
vexpress machine, or the QEMU driver.
Signed-off-b
Edited for brevity. Full version:
$ git fetch https://gitlab.com/abologna/libvirt.git qemu-caps
Andrea Bolognani (2):
tests: Don't use features with vexpress machine
tests: Add capabilities for QEMU 8.2.0 on aarch64
.../qemu_8.2.0-virt.aarch64.xml | 227 +
tests/domaincaps
On Mon, 8 Jan 2024 18:42:19 +0530 (IST)
Vivek Kashyap wrote:
> ...
> >> As I've stated above, for libvirt we should consider only passing it via
> >> the 'secret' object.
>
> Sounds good. Will follow this up.
>
> Alex - will you be working on the qemu update?
I'm not the one driving a use c
The full functionality was merged into qemuxmlconftest.
Signed-off-by: Peter Krempa
---
docs/advanced-tests.rst | 2 +-
tests/meson.build | 1 -
tests/qemucapabilitiesdata/README.rst | 2 +-
.../qemuxml2argvdata/mach-virt-serial-usb
Since this tests inactive/config XML files rename it accordingly.
Signed-off-by: Peter Krempa
---
docs/advanced-tests.rst | 10 +-
src/util/virsecret.c| 2 +-
tests/meson.build | 2 +-
tests/qemucapabilit
Don't special-case qemuxml2argvtest's handling of timeout but rather
allow each test array entry to have it's own.
Signed-off-by: Peter Krempa
---
tests/meson.build | 10 ++
1 file changed, 2 insertions(+), 8 deletions(-)
diff --git a/tests/meson.build b/tests/meson.build
index 4a404237
This is an intermediate step to merge qemuxml2xmltest into this common
helper. This eliminates double setup/parsing of the input data as well
as will ensure that all input XMLs are tested both for ARGV as well as
XML output. For now we skip tests that don't have an output XML to show
that the this
Extract the common setup and parsing of the input XML into a separate
helper testQemuConfXMLCommon(). The helper has semantics which will
allow us to call it from multiple places so that VIR_TEST_RANGE will
still work properly even when we'll add multiple steps reusing the
prepared data.
Signed-of
Get clean separation between the parsing and argv conversion so that
it's obvious in the test output:
2409) QEMU XML def parse s390-async-teardown.s390x-6.0.0...
libvirt: QEMU Driver error : unsupported configuration: asynchronous teardown
is not available with this QEMU binary
O
Move the setup of the fake driver from testCompareXMLToArgv to 'mymain'.
With this we also won't need to reset the fake drivers which was done
only partially.
Signed-off-by: Peter Krempa
---
tests/qemuxml2argvtest.c | 34 --
1 file changed, 16 insertions(+), 18 de
Prior to all tests being converted to "DO_TEST_CAPS*" invocation the
fake-caps tests required knowing the architecture, which was pre-parsed
in qemuxml2argvtest. This code was now removed, but the arch parser was
forgotten.
Signed-off-by: Peter Krempa
---
tests/qemuxml2argvtest.c | 8
1
In previous patches we've added testing of XML's explicitly parsed as
active (ensuring that it e.g. has a domain id) formatted into both
active and inactive versions.
Now qemuxml2xmltest can be simplified by making it test only XMLs parsed
as inactive.
To do this we pass VIR_DOMAIN_DEF_PARSE_INAC
As we don't do any additional parsing of the input file in
qemuxml2argvtest we can simplify the code.
Signed-off-by: Peter Krempa
---
tests/qemuxml2argvtest.c | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/tests/qemuxml2argvtest.c b/tests/qemuxml2argvtest.c
index 226f
Add explicit test cases for XMLs from qemuxml2argvdata which
historically had different output in qemuxml2xmltest.
qemuxmlactivetest explicitly ensures that the input XMLs are parsed in
'live' state and formatted both in inactive as well as live state,
rather than the previously present inactive->
'virDomainDefFormatInternalSetRootName' which is the top level XML
formatter function has the following condition as the very first thing:
if (def->id == -1)
flags |= VIR_DOMAIN_DEF_FORMAT_INACTIVE;
This makes it pointless to separately do inactive->active and
inactive->inactive XML
Neither qemuxml2argvtest nor qemuxml2xmltest now test configs parsed as
active, thus this flag is no longer needed.
Signed-off-by: Peter Krempa
---
tests/qemuxml2argvtest.c | 3 +--
tests/qemuxml2xmltest.c | 13 +
tests/testutilsqemu.h| 3 +--
3 files changed, 7 insertions(+),
Currently the xml->xml testing we have in qemuxml2xmltest covers only 3
of the 4 possibilities:
By invocation:
active -> active;
inactive -> inactive;
by unintentionally:
active -> inactive (for configs which don't set an 'id' as the
formatter assumes it's inactive)
TL;DR: Patch 23/23 is optional, read below!
This patch saga aims to improve and simplify testing of qemu XML
configs.
Part 1 ensured that all input XMLs are invoked from qemuxml2argvtest
In part 2 I've focused on untangling xml->xml testing, explaining and
cleaning up cases which don't make sens
Refactor the code so that the test macros invoke a helper function with
no additional steps. This change prevents regressions in compilation
time when adding extra steps for the tests, which happen when the test
macro gets too complicated.
Signed-off-by: Peter Krempa
---
tests/qemuxml2argvtest.c
The typedef will come in handy to create an autoptr cleaning function
later on.
Signed-off-by: Peter Krempa
---
tests/qemuxml2argvtest.c | 14 +++---
tests/qemuxml2xmltest.c | 12 ++--
tests/qemuxmlactivetest.c | 6 +++---
tests/testutilsqemu.c | 6 +++---
tests/testutil
The test will be testing both status XMLs and active XMLs. Rename it to
a shorter name.
Signed-off-by: Peter Krempa
---
tests/meson.build | 2 +-
tests/{qemustatusxml2xmltest.c => qemuxmlactivetest.c} | 0
2 files changed, 1 insertion(+), 1 deletion(-)
renam
Get rid of the extra temporary variable and set the parse and format
flags based on liveness together.
Signed-off-by: Peter Krempa
---
tests/testutils.c | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/tests/testutils.c b/tests/testutils.c
index 6ee78cca3c..8d4e7f84bf
The main idea of the test is to validate config when PCIe is compiled
out.
Signed-off-by: Peter Krempa
---
.../riscv64-virt.riscv64-latest.xml | 20 ++-
tests/qemuxml2xmltest.c | 5 -
2 files changed, 6 insertions(+), 19 deletions(-)
diff --g
Index is auto-allocated normally. Additionally we now don't need the
extra active/inactive version of this test.
Signed-off-by: Peter Krempa
---
tests/qemuxml2argvdata/disk-network-nfs.xml | 2 +-
...isk-network-nfs-inactive.x86_64-latest.xml | 55 ---
.../disk-network-nfs.x86
The test case requires an exception in virschematest as the output file
is no longer invalid.
Signed-off-by: Peter Krempa
---
...une-auto-nodeset-invalid.x86_64-latest.xml | 44 +++
tests/qemuxml2xmltest.c | 1 +
tests/virschematest.c
The exception is needed in qemuxml2xmltest which is in one instance
testing update from an invalid config to a valid one. Currently the
compliance with the test is achieved via a hack.
As further patches will be simpler without the hack present we need a
way to invert the expected output in specif
...
As I've stated above, for libvirt we should consider only passing it via
the 'secret' object.
Sounds good. Will follow this up.
Alex - will you be working on the qemu update?
Forgot to add:
If you need a way to test it with a libvirt-started VM in the interim
until the qemu commandline
On Mon, Jan 08, 2024 at 12:07:16PM +, Daniel P. Berrangé wrote:
> On Mon, Jan 08, 2024 at 02:57:40AM -0800, Andrea Bolognani wrote:
> > On Mon, Jan 08, 2024 at 11:54:00AM +0100, Peter Krempa wrote:
> > > On Mon, Jan 08, 2024 at 11:43:24 +0100, Andrea Bolognani wrote:
> > > > +++ b/ci/integratio
On Mon, Jan 08, 2024 at 02:57:40AM -0800, Andrea Bolognani wrote:
> On Mon, Jan 08, 2024 at 11:54:00AM +0100, Peter Krempa wrote:
> > On Mon, Jan 08, 2024 at 11:43:24 +0100, Andrea Bolognani wrote:
> > > These are special in that, when a new target is introduced, some
> > > preparation is needed be
On Mon, Jan 08, 2024 at 12:44:01 +0100, Peter Krempa wrote:
> On Mon, Jan 08, 2024 at 17:05:45 +0530, Vivek Kashyap wrote:
> > >
> > > If there is even a slight expectation of confidentiality (IMO just
> > > calling it a 'secret' in documentation is enough to justify that
> > > expectation) it sho
On Mon, Jan 08, 2024 at 17:05:45 +0530, Vivek Kashyap wrote:
> >
> > If there is even a slight expectation of confidentiality (IMO just
> > calling it a 'secret' in documentation is enough to justify that
> > expectation) it should be treated as such.
> >
> > Thus qemu needs to add the possibilit
If there is even a slight expectation of confidentiality (IMO just
calling it a 'secret' in documentation is enough to justify that
expectation) it should be treated as such.
Thus qemu needs to add the possibility to pass it via the 'secret'
object, so that libvirt can pass it encrypted. On the
On Mon, Jan 08, 2024 at 11:54:00AM +0100, Peter Krempa wrote:
> On Mon, Jan 08, 2024 at 11:43:24 +0100, Andrea Bolognani wrote:
> > These are special in that, when a new target is introduced, some
> > preparation is needed before the changes can be merged. Since
> > this only happens every six mont
On Mon, Jan 08, 2024 at 11:43:24 +0100, Andrea Bolognani wrote:
> These are special in that, when a new target is introduced, some
> preparation is needed before the changes can be merged. Since
> this only happens every six months or so, it's unsurprising that
> we keep messing it up and forgettin
On Mon, Jan 08, 2024 at 10:48:58AM +0100, Peter Krempa wrote:
> On Mon, Jan 08, 2024 at 10:35:53 +0100, Peter Krempa wrote:
> > On Thu, Dec 14, 2023 at 09:28:15 +0100, Michal Privoznik wrote:
> > > Green pipeline:
> > >
> > > https://gitlab.com/MichalPrivoznik/libvirt/-/pipelines/1106643445
> > >
>
These are special in that, when a new target is introduced, some
preparation is needed before the changes can be merged. Since
this only happens every six months or so, it's unsurprising that
we keep messing it up and forgetting some steps. Having notes
right in the file will hopefully help going f
These are jobs are supposed to be running tests using a QEMU
binary built from the latest upstream sources, but right now
they're just doing the same thing as the other jobs for the
target. Use the correct job templates.
Signed-off-by: Andrea Bolognani
---
ci/integration.yml | 4 ++--
1 file cha
Signed-off-by: Andrea Bolognani
---
ci/integration.yml | 42 +-
1 file changed, 21 insertions(+), 21 deletions(-)
diff --git a/ci/integration.yml b/ci/integration.yml
index c234696d10..ff1bb5d81d 100644
--- a/ci/integration.yml
+++ b/ci/integration.yml
@@
Andrea Bolognani (3):
ci: Fix upstream-qemu job definitions
ci: Move upstream-qemu job to Fedora 39
ci: Add notes for integration jobs
ci/integration.yml | 58 +++---
1 file changed, 39 insertions(+), 19 deletions(-)
--
2.43.0
On Mon, Jan 08, 2024 at 10:35:53 +0100, Peter Krempa wrote:
> On Thu, Dec 14, 2023 at 09:28:15 +0100, Michal Privoznik wrote:
> > Green pipeline:
> >
> > https://gitlab.com/MichalPrivoznik/libvirt/-/pipelines/1106643445
> >
> > Michal Prívozník (2):
> > ci: integration: Switch upstream integrat
On Thu, Dec 14, 2023 at 09:28:15 +0100, Michal Privoznik wrote:
> Green pipeline:
>
> https://gitlab.com/MichalPrivoznik/libvirt/-/pipelines/1106643445
>
> Michal Prívozník (2):
> ci: integration: Switch upstream integration tests to Fedora 39
For future reference, please note that the integra
On 08.01.24 09:38, Peter Krempa wrote:
On Fri, Jan 05, 2024 at 18:30:56 +0100, David Hildenbrand wrote:
On 05.01.24 14:58, Peter Krempa wrote:
On Fri, Jan 05, 2024 at 14:34:53 +0100, David Hildenbrand wrote:
On 05.01.24 13:40, Peter Krempa wrote:
On Fri, Jan 05, 2024 at 13:33:32 +0100, Michal
On Fri, Jan 05, 2024 at 18:30:56 +0100, David Hildenbrand wrote:
> On 05.01.24 14:58, Peter Krempa wrote:
> > On Fri, Jan 05, 2024 at 14:34:53 +0100, David Hildenbrand wrote:
> > > On 05.01.24 13:40, Peter Krempa wrote:
> > > > On Fri, Jan 05, 2024 at 13:33:32 +0100, Michal Privoznik wrote:
[...]
82 matches
Mail list logo
