aboutsummaryrefslogtreecommitdiff
path: root/hw/avr/arduino.c
diff options
context:
space:
mode:
authorThomas Huth <thuth@redhat.com>2025-04-14 13:30:28 +0200
committerThomas Huth <thuth@redhat.com>2025-04-23 07:51:25 +0200
commitf8c54844175922d77faa8b586f451e379d53a191 (patch)
tree0dbb4b87a0d7e615105c6c55aedd883490d0dd6c /hw/avr/arduino.c
parent5c2bae2155b162f7355ca759881c5fdaaf7bc209 (diff)
downloadqemu-f8c54844175922d77faa8b586f451e379d53a191.zip
qemu-f8c54844175922d77faa8b586f451e379d53a191.tar.gz
qemu-f8c54844175922d77faa8b586f451e379d53a191.tar.bz2
gitlab-ci: Update QEMU_JOB_AVOCADO and QEMU_CI_AVOCADO_TESTING
Since we don't run the Avocado jobs in the CI anymore, rename these variables to QEMU_JOB_FUNCTIONAL and QEMU_CI_FUNCTIONAL. Also, there was a mismatch between the documentation and the implementation of QEMU_CI_AVOCADO_TESTING: While the documentation said that you had to "Set this variable to have the tests using the Avocado framework run automatically", you indeed needed to set it to make the pipelines appear in your dashboard - but they were never run automatically in forks and had to be triggered manually. Let's improve this now: No need to hide these pipelines from the users by default anymore (the functional tests should be stable enough nowadays), and rather allow the users to run the pipelines auto- matically with this switch now instead, as was documented. Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> Message-ID: <20250414113031.151105-15-thuth@redhat.com> Signed-off-by: Thomas Huth <thuth@redhat.com>
Diffstat (limited to 'hw/avr/arduino.c')
0 files changed, 0 insertions, 0 deletions