action #61801
open[opensuse][aarch64] Tests to run on aarch64 real hardware (RPi3/4)
0%
Description
Once https://progress.opensuse.org/issues/60518 is done to enable tests in RPi3 and/or RPi4, we need to add hardware to o3 and, we could run the following tests:
-
- donejeos
-
jeos-extra
- done inDevelopment > Tumbleweed
only due to test failures -
- donejeos_extra_tests_ai_ml
-
on RPi4 - donejeos_extra_tests_vagrant
- Other
textmode
tests? Maybeautoyast_minimal
and/orinstall_only
(with ISO installer), in SSH mode (ssh=1
option for linuxrc), but it may require some work.
Updated by ggardet_arm over 5 years ago
- Blocked by coordination #60518: [functional][u][rpi][epic] Add support for real systems without IPMI or KVM-IP in openQA/os-autoinst added
Updated by okurz over 5 years ago
- Subject changed from Tests to run on aarch64 real hardware (RPi3/4) to [opensuse][aarch64] Tests to run on aarch64 real hardware (RPi3/4)
Updated by ggardet_arm about 5 years ago
I currently have the following tests running on RPi3 (B and Bplus) on my local openQA setup:
-
RPi_flash_firmware
to workaround https://github.com/raspberrypi/firmware/issues/1322 jeos
jeos-extra
jeos_extra_tests_ai_ml
jeos_extra_tests_vagrant
Updated by ggardet_arm almost 5 years ago
- Description updated (diff)
- Status changed from New to In Progress
- Assignee set to ggardet_arm
The following Tumbleweed tests are green:
-
RPi_flash_firmware
: https://openqa.opensuse.org/tests/1259118 -
jeos
: https://openqa.opensuse.org/tests/1259990 -
jeos_extra_tests_ai_ml
: https://openqa.opensuse.org/tests/1261203
Updated by okurz over 3 years ago
This ticket was set to "Normal" priority but was not updated within the SLO period for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives. Please consider picking up this ticket within the next 365 days or just set the ticket to the next lower priority of "Low" (no SLO related time period).
Updated by slo-gin over 2 years ago
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
Updated by slo-gin about 1 year ago
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
Updated by slo-gin about 2 months ago
- Priority changed from Normal to Low
This ticket was set to Normal priority but was not updated within the SLO period. The ticket will be set to the next lower priority Low.