test(infra): replace qemu with docker client in integration tests#2908
test(infra): replace qemu with docker client in integration tests#2908p-targowicz wants to merge 1 commit into
Conversation
|
@mender-test-bot start integration pipeline |
|
Hello 😺 I created a pipeline for you here: Pipeline-2555452142 Build Configuration Matrix
|
|
@mender-test-bot start integration pipeline |
|
Hello 😺 I created a pipeline for you here: Pipeline-2555802956 Build Configuration Matrix
|
64a69e3 to
0630c7e
Compare
|
@mender-test-bot start integration pipeline |
|
Hello 😺 I created a pipeline for you here: Pipeline-2555953446 Build Configuration Matrix
|
0630c7e to
436e2d9
Compare
|
@mender-test-bot start integration pipeline |
|
Hello 😺 I created a pipeline for you here: Pipeline-2557009758 Build Configuration Matrix
|
|
@p-targowicz, start a full integration test pipeline with:
my commands and optionsYou can prevent me from automatically starting CI pipelines:
You can trigger a client pipeline on multiple prs with:
You can trigger a client pipeline for a specific Mender Client release with:
You can trigger GitHub->GitLab branch sync with:
You can print PR statistics for a repository with:
You can cherry pick to a given branch or branches with:
|
44a61d8 to
40e5552
Compare
|
@mender-test-bot start integration pipeline |
|
Hello 😺 I created a pipeline for you here: Pipeline-2557235028 Build Configuration Matrix
|
Migrated test_bootstrapping (test_bootstrap), test_preauth (all OS tests), and test_grouping (test_basic_groups) to use Docker-native client fixtures instead of QEMU. Added infrastructure to make this possible: - DockerComposeDockerClientSetup now accepts num_clients for scaling - DockerComposeEnterpriseDockerClientSetup tracks client count so repeated new_tenant_docker_client calls scale up incrementally - New fixtures: standard_setup_two_docker_clients_bootstrapped, enterprise_one_docker_client, enterprise_two_docker_clients_bootstrapped - helpers._check_log_for_message falls back to D-Bus auth check on devices without systemd (Docker client uses supervise loop, not systemd) - Client.__wait_for_keygen in test_preauth tries both /data/mender and /var/lib/mender key paths, covering QEMU and Docker layouts Tests that require A/B rootfs partitions, real reboots, or bootloader behavior remain on QEMU. Ticket: QA-1639 Signed-off-by: Patryk Targowicz <patryk.targowicz@northern.tech>
40e5552 to
23dda4a
Compare
|
@mender-test-bot start integration pipeline |
|
Hello 😺 I created a pipeline for you here: Pipeline-2558132949 Build Configuration Matrix
|
Qemu containers boot a full Yocto OS which takes ~45s and eats a lot of memory. Switch the standard, signed-artifact, short-lived token, failover and MTLS setups to use the docker-native client instead. Also update enterprise new_tenant_client to use the docker client, cutting the post-start sleep from 45s to 5s.
For tests that genuinely need A/B rootfs behaviour, add an explicit DockerComposeQemuClientSetup class and a qemu_setup_one_client fixture they can opt into.
Ticket: QA-1639